Article
Against Shiny-Object Architecture
New tools deserve evaluation, not automatic adoption or automatic rejection.
Deliver. Business. Value.
Notes from building things that had to survive first contact with reality.
What worked. What didn't. The cost of learning the difference between the two.
Operating stance
Change is the default condition.
Good systems are not made by chasing every new surface area or flattening every disagreement into committee language. They are made by naming volatility, keeping options open where change is likely, and choosing proven mechanisms where behavior is already well-understood.
Field notes
Featured Writing
One entry that anchors the current direction of the site.
Field notes
Latest Writing
Concise notes on architecture, AI, complexity, and the work of staying intellectually honest.
Statistical Inference ≠ Judgement
Guessing is not judgement.
Build for Change
Systems last longer when change is expected and visible instead of hidden behind optimism and wishful thinking.
Beyond the Obvious
The first answer is often a reflection of the current framing, not the real design problem.
Principles and Pragmatism
Principles matter most when they remain accountable to real outcomes.
Against Shiny-Object Architecture
New tools deserve evaluation, not automatic adoption or automatic rejection.
Design by Committee Is Not Collaboration
Consensus can improve a design, but it can also dilute accountability and erase the real tradeoff.
Field notes
Active Series
Recurring threads without a heavy taxonomy.
Projects