Boring Solutions: Strategy for Sustainable Engineering
In today's software engineering, I see a central conflict: that almost magnetic attraction to new technologies versus the solidity of systems that have been around for ages. We often find ourselves torn, seduced by tools that promise magical solutions, while our experience warns us about the hidden costs of everything new. In this series of articles, I want to show that curbing the technological hype a bit doesn't hinder innovation. On the contrary, it is what truly makes it happen. After all, where does real agility in engineering come from? It comes from the deep mastery of a stable and hand-picked set of tools, not from this endless race after the latest novelty. Behind this idea lies a fundamental psychological pillar: a mindset that values learning deeply rather than just jumping from trend to trend.
To develop this thought, we will lean on four pillars that, together, create a solid foundation for those who lead technology.
- First, I explore Dan McKinley's philosophy, "Choose Boring Technology". We will see how this is a very smart strategy to manage risks and decide where to spend our resources.
- Second, we analyze Colonel John Boyd's "Law of Iteration." It is a military principle that shows how iteration speed becomes a crucial competitive advantage for those who develop software.
- Third, we will see how these concepts work in practice using GitLab as an example. They attribute their impressive release pace precisely to their preference for "boring solutions."
- Finally, we bring this philosophy into the current world through Aaron Brethorst's vision. He argues that the arrival of Artificial Intelligence (AI) coding assistants makes the principles of boring technology even more vital.
After going through these points, I want to show how to apply these concepts when deciding which technologies to adopt. The goal is to create clear criteria to evaluate new tools and keep the architecture consistent over time.
By connecting these pillars, you will have a practical guide to building an engineering organization that is sustainable, productive, and truly innovates. Are we ready to choose what works instead of what is merely "new"?