Remember that in any organisation, people make decisions — decisions are about trade-offs, and decisions can be influenced, overturned, and changed. More importantly, organisations evolve— the way decisions were made yesterday might not be the way they get made tomorrow!

An uncommonly sophisticated piece of how to think about technical debt and how to tackle it organizationally. It already starts off right by not using a debt-is-money comparison.

One of the points in this list by Paul Osman that I recently stumbled on is that things like “staging” are indeed mostly useless however much people want to keep using them.

I’m glad that this takedown of Clean Code by Dan Abramov got so much traction. I have no problem with clean code (lowercase), but inevitably the process of getting there and the things people do as a consequence make the entire endeavor an anti-pattern.

“Obsessing with “clean code” and removing duplication is a phase many of us go through. When we don’t feel confident in our code, it is tempting to attach our sense of self-worth and professional pride to something that can be measured. A set of strict lint rules, a naming schema, a file structure, a lack of duplication.”

As always, people get too attached to the parts that are the most obvious and the least important.