Why software ends up complex · Alex Gaynor

Featuritis. The besetting temptation for the architect of a general purpose tool such as a spreadsheet or a word processor is to overload the product with features of marginal utility, at the expense of performance and even of ease of use. The appeal of proposed features is evident at the outset; the performance penalty is evident only as system te

... See more

People who see complicated solutions do not have an incentive to implement simplified ones. As we saw, a bureaucratized system will increase in complication from the interventionism of people who sell complicated solutions because that’s what their position and training invite them to do. Things designed by people without skin in the game tend to g

... See more

The key to building complex systems is not designing complexity from the start. Instead, it’s about building simple systems, allowing them to fail, and iterating on those systems based on what works and what does not work.

You've probably heard the advice that software as a field is changing all the time , and that you shouldn't get swept up in the framework treadmill, just focus on learning fundamental skills. This is a true, but doesn't explain the "why". For structural reasons, information in software propagates really quickly. This is due to a lot of factors (int

... See more

Every software system provides two different values to the stakeholders: behavior and structure. Software developers are responsible for ensuring that both those values remain high. Unfortunately, they often focus on one to the exclusion of the other. Even more unfortunately, they often focus on the lesser of the two values, leaving the software sy

... See more