Why an engineers keeps a blog

The architecture diagrams stay on the internal wiki; the trade-offs get argued out in a meeting and then quietly forgotten. This is where I do the opposite — work through ideas in the open meaning let the stakeholders rant their heart out, and go build something about it.

What I'll write about

Roughly the things I've learned new'

• Decisions and the reasoning behind them, not just the outcome.
• The boring constraints — compliance, cost, change management — that shape real architecture.
• Occasionally, a war story with the names filed off.

The best architecture writing explains a choice well enough that a reader can disagree with it.