Tech Stack

Proven Technology Lowers Maintenance Cost

A tech stack is the combination of programming languages, frameworks, databases, and infrastructure tools on which an application is based. The choice of stack is a long-term economic decision: it determines the availability of skilled staff, how high maintenance costs become, and how quickly an organisation can react to market changes.

Boring Technology uses proven technologies for the stable core of a system. New or riskier tooling belongs where it creates a clear business advantage.

Anti-Patterns: The Trend Trap

• Resume Driven Development: Developers choose technologies only because they want them on their resume, not because they are the best solution for the problem.
• Framework Chasing: Constant switching to the latest framework, leading to a fragmented architecture that nobody fully understands anymore.
• Technology Zoo: Every team uses a different programming language or database. This makes knowledge sharing harder and increases operating costs.

The Curated Stack

1. Targeted room for change: New or riskier technologies are used only when a concrete business benefit or differentiating advantage is supported by evidence.
2. Standardisation (Golden Paths): Definition of a standard stack for new projects. Deviations are justified with Architecture Decision Records (ADRs).
3. Ecosystem Check: Technologies need a large community, good documentation, and a long support horizon (LTS).
4. Managed Services: Cloud services handle standard components (e.g. PostgreSQL as a managed DB) instead of running them manually.
5. Polyglot Persistence (with restraint): Using the right database for the right purpose (e.g. search via Elasticsearch, data via SQL), but without unnecessarily expanding the zoo.

The Focus: Long-Term Maintainability

A good tech stack is like a well-organised toolbox: the right tool is available for each task, but not ten variants of the same tool.

FAQ

Does an organisation lose good specialists if it does not always use the latest technology?

Stable systems and clear guardrails are attractive to many experienced specialists. People who join only because of a specific framework often stay only until the next technology shift.

Can older technology still support fast feature delivery?

Yes, usually even faster. Proven technologies have fewer bugs, better libraries, and more available team experience. This saves time when tracking down errors.

References

• McKinley, Dan Choose Boring Technology. Case for proven technologies and justified deviations from the standard. (2015). mcfunley.com/choose-boring-technology
• Thoughtworks Technology Radar. Systematic evaluation of technological trends. www.thoughtworks.com/radar
• StackShare Tech Stacks. Insights into the technology choices of successful companies. stackshare.io