I saw that talk at an Agile conference earlier this year. really good. he also recommended the book Accelerate during it, which I think is the most interesting non-technical book I’ve ever read on software engineering practices

Inverted classes: the whole lectures have already been recorded in video, the class are about answering questions and live problem solving

A good article presenting a Git branching model for development roadmap

Algorithm to the multi-armed bandit.

One strategy that has been shown to perform well time after time in practical problems is the epsilon-greedy method. We always keep track of the number of pulls of the lever and the amount of rewards we have received from that lever. 10% of the time, we choose a lever at random. The other 90% of the time, we choose the lever that has the highest expectation of rewards.

Quote from one of the top comment (https://news.ycombinator.com/item?id=19957326)

And some of my favorite simplifying patterns:

• AOP for logging; but NOT (dear god) for business logic.

• 3 levels of abstraction, and no more. If you can't figure out a way to do it in 3 levels of abstraction, then something else is wrong.

• 3 systems of state: config (global), current request and persistence (database). If you need more than that, then something is wrong with the architecture. (Ok, compilers may not be able to get away with this, but most applications can, in my experience.)

• If you use a pattern (MVC, for example) apply it to the whole system. E.g. doing IOC only in the upstream API system when the rest of the code doesn't, just makes a mess.

Very nice books written about the history of the most famous games

Interesting article on how to lock resources

TL;DR

A bunch of tips for using PostgreSQL

Our boss, in on the conspiracy with us, had thoughtfully recommended that we randomize the order of the browsers listed

That's an interesting point.

From HN

Good, intuitive introduction to matrices. Next steps could be showing that there are infinitely many different matrix representations of a linear map (different from the polynomials) and they can be used for function spaces, too.

TIL about oneshot coverage. Which could be used in production to identify dead-end code.

An essential read (that I need to do)

That was driving me crazy. TL;DR

git config --global pager.branch false

Another good read

Need to understand some implication of Ruby and the memory.

Interesting implementation of the String API for Billing (recurring)

Definitely need to dive into streams one of these days