Featured
Denormalising trades write complexity for read speed, and the bill arrives later. Four questions decide when a copy is worth it, and how to keep it honest.
11 min
Topic 08 / 08 · 03 articles
About this topic
113 words
Some of the most useful engineering knowledge is not about any specific technology. It is about how to decide and how to hand work over: when copying data is worth the cost of keeping it honest, how to write a spec that another engineer or a coding agent can execute without guessing, and how to review an incident so the fix actually lands.
This topic is my architect’s notebook — opinionated pieces that each take one recurring question and answer it with the reasoning and the trade-offs behind my answer.
If you lead a team or make architecture calls on your own, these are the articles most likely to save you a week.
Featured
Denormalising trades write complexity for read speed, and the bill arrives later. Four questions decide when a copy is worth it, and how to keep it honest.
11 min
· 9 min
Most incident reviews end as documents nobody opens again. A one-page format, actions filed as ordinary issues and a thirty-day check make change likely.
9 min
· 12 min
An agent does what the spec says, not what you meant. Scope, named files and an executable check turn a long unattended session into a reviewable diff.
12 min
· 11 min
Denormalising trades write complexity for read speed, and the bill arrives later. Four questions decide when a copy is worth it, and how to keep it honest.
11 min