Topic guide · 01

Architecture

Systems are shaped less by their diagrams than by the decisions nobody revisits. This guide follows three of them: what to keep boring, what convenience really costs, and how to replace a monolith without betting the company.

3 essays 17 min read Curated path

The argument

Start here
  1. Boring is a budget

    Novelty is finite. Spend it where it changes the product, and make the rest unremarkable enough that nobody has to think about it.

  2. Convenience is a loan

    Every abstraction borrows against future understanding. The interest comes due when the abstraction leaks, and someone has to own a dependency they never chose.

  3. A rewrite is a bet; a seam is a hedge

    You rarely understand the old system better than its builders. Strangle it one route at a time, with a clean seam and a rehearsed rollback.

All essays in this guide

Tag archive →
Jun 02, 2026 The Case for Boring Architecture Every team wants the interesting choice. The interesting choice is usually the one you pay for at 3 a.m., with interest. architecture 6 min Aug 18, 2026 The Hidden Cost of Convenience Convenience is a loan. The interest stays invisible until the abstraction you did not understand needs to change — and you own a dependency you never chose. career · architecture 5 min Jul 20, 2026 What I Learned Rewriting a Monolith A rewrite is a bet that you understand the old system better than its builders. The safer path is a migration with a clean seam and a rehearsed rollback. architecture · devops 6 min

Continue with Performance

Open guide →

Architecture decides what the system costs to change. Performance decides what it costs to use. The Performance guide follows the same method: measure the population, fix the tail, and reserve space before the browser has to guess.

Search essays