One Way Smart Developers Make Bad Strategic Decisions

So now, when I hear about top-down standardization efforts, I get a little worried because I know that trying to generalize across many problems is a fraught endeavor. What’s better is getting to know a specific problem by working collaboratively and embedding with the people who have the most tacit knowledge of the problem. Standardization and top-down edicts fail when they miss or ignore the implicit understandings of people close to the problem

Hints for writing Unix tools

General good advice on how to design unix tools. I summarize it as: “Design your unix tools to be composable”.

The Code Review Pyramid

The graphic speaks for itself: Spend more time in the bottom, than at the top. Automate what is possible.