Engineering philosophy • 4 minute read •
Build leverage, not just software
Four durable principles for reducing friction without turning every problem into more software.
Read the philosophyInsights
Engineering philosophy and field notes
The reasoning behind how I choose problems, design for leverage, preserve human judgment, and evaluate whether a system is useful.
Engineering note • 5 minute read •
Why does this still require me?
A practical test for recognizing repeated work that should become a system, a delegated responsibility, or an automated workflow.
Read the noteDistributed systems • 4 minute read •
Complexity changes address
A decision heuristic for tracking the failure modes and responsibilities that an optimization moves elsewhere.
Read the noteDistributed systems • 5 minute read •
What if Git had no master branch?
A limited analogy for understanding blockchain as a shared-history and consensus problem.
Read the articleEngineering leadership • 4 minute read •
Ownership starts before escalation
A practical standard for making meaningful issues, risk, and next actions visible before someone has to ask.
Read the noteOperational intelligence • 5 minute read •
Release reports become operational history
How comparable release snapshots can reveal longer-term patterns without replacing engineering judgment.
Read the note