Tim Oxley

It's easy to throw stones at whatever-the-trendiest-thing-is, which I am doing, because it also contains 99% of novices.

Or perhaps the mummified head of a goblin. Perhaps both.

if you don't need it, don't code it! If you need to add that feature later, do so at that point.

A simple way to be a better engineer, enjoy perf benefits, and move faster, is to not over-engineer your code.

the inverse bus factor: how many people must be hit by a bus for the project to make progress

This is a good article about CSS http://mrmrs.io/writing/2016/03/24/scalable-css/ … from @mrmrs_

I will say this: These "no true developer" dudes always draw the cutoff point for "real developer" right at the boundary of their own skill

But I guess hands will learn the correct positions eventually.

Trying to adjust volume or brightness tends to either change wrong one, mute or open a "do you want to enable Siri" dialog. Pretty crappy

MacBook pro touch bar vs vim ESC key verdict: no issue at all. It's fine. Adjusting volume/brightness without looking is problematic though.

Stop extracting single-use components

Once things start solidifying and boundaries are clear *inside* the monolith, you can think about starting to separate the pieces.

People use the word "monolith" as a epithet, but if your boundaries need to be easy to change, a monolith is your best architecture choice.

So much pathology in software comes from small teams adopting process made for large teams. Five developers in a startup don't need gerrit

People run into trouble with DRY because it doesn't tell you *what* not to repeat. People assume syntax, but it's actually concepts.

Abstraction trades an increase in real complexity for a decrease in perceived complexity. That isn't always a win.