Design patterns and anti-patterns that separate maintainable codebases from technical debt graveyards.

Discover the recurring themes in software's grand narrative, where solutions echo across languages and decades of development wisdom. These pattern explorations reveal why some approaches stand the test of time while others become cautionary tales shared over retrospectives.

Archive2026 (10)2025 (11)2024 (5)2023 (11)All (37)Topics (13)

Patterns

8 articlesOther topics →

NaN: the number that poisons every calculation it touches

NaN looks like a harmless floating-point oddity until it crosses a boundary. One invalid calculation can become a missing chart, a corrupt aggregate, a broken equality check, or a model training run that quietly collapses.

16 May 2026 · 12 min read · Quality, Standards, PatternsRead →

The microservices tax: when distributed systems cost more than the problems they solve

The industry adopted microservices as the default architecture for modern systems, but the tax is coming due. When the company that helped popularise distributed services publishes a 90% cost reduction by returning to a monolith, the assumption deserves reexamination.

15 February 2026 · 16 min read · Architecture, Patterns, Infrastructure, DevOpsRead →

Null: the billion-dollar mistake that keeps compounding

In 1965, a computer scientist added a feature to a programming language because it was easy to implement. Sixty years and countless production crashes later, every modern language designed for reliability has arrived at the same conclusion: that decision was catastrophically wrong.

5 January 2026 · 6 min read · Quality, Patterns, StandardsRead →

The architecture autopsy: when 'we'll refactor later' becomes 'we need a complete rewrite'

Early architectural decisions compound over time, creating irreversible constraints that transform minor technical debt into catastrophic system failures. Understanding how seemingly innocent choices cascade into complete rewrites reveals why future-proofing architecture requires balancing immediate needs with long-term reversibility.

23 October 2025 · 11 min read · Architecture, Patterns, QualityRead →

The symptom-fix trap: Why patching consequences breeds chaos

In the relentless pressure to ship features and fix bugs quickly, development teams fall into a destructive pattern of treating symptoms rather than root causes. This reactive approach creates cascading technical debt, multiplies maintenance costs, and transforms codebases into brittle systems that break under the weight of accumulated shortcuts.

28 August 2025 · 19 min read · Quality, Patterns, StandardsRead →

Technical debt triage: making strategic compromises

Simple CSV export: one day estimated, three weeks actual. User data spread across seven tables with inconsistent types—strings, epochs, ISO 8601 timestamps. Technical debt's real cost isn't messy code; it's velocity degradation. Features take weeks instead of days. Developers spend 17 hours weekly on maintenance from accumulated debt.

21 July 2025 · 12 min read · Quality, Architecture, Standards, PatternsRead →

Avoiding overkill: embracing simplicity

A contact form implemented with React, Redux, Webpack, TypeScript, and elaborate CI/CD pipelines—2.3MB production bundle for three fields and a submit button. Two days to set up the development environment. Thirty-five minutes to change placeholder text. This is overengineering: enterprise solutions applied to problems that need HTML and a server script.

22 November 2024 · 10 min read · Architecture, Patterns, QualityRead →

Floating point: the maths your computer quietly gets wrong

Most developers learn that 0.1 plus 0.2 looks strange, then quietly file it under language trivia. The real lesson is sharper: computers do not store numbers the way humans write them, and consequences compound.

20 March 2023 · 11 min read · Standards, Patterns, QualityRead →