The Architect's Era: AI Changed Who Writes the Code

Something fundamental has shifted. The craft of building web applications no longer lives in the typing — in memorizing API signatures, wrestling with CSS specificity, or hand-rolling state management. AI writes that code now, and it writes it fast.

But here's what hasn't changed: someone still needs to know what to build and why. Someone needs to understand that a naive database query will collapse under load, that an eventually-consistent cache will serve stale data to users who just clicked "save," that a synchronous call to a third-party service is a latency bomb waiting to go off.

The tools got better. The knowledge didn't get optional.

If anything, the bar is higher now. When you can scaffold an entire application in an afternoon, the bottleneck isn't implementation — it's judgement. Knowing when to shard versus replicate. Knowing why your p99 latency matters more than your average. Knowing that the "simple" solution the AI suggested will fall apart the moment you need to deploy it across regions.

We don't write code the way we used to. But we need to understand systems more than ever. This site is about that understanding — the high-level thinking that no autocomplete can replace.