Source & Architecture
Keeping Data Contracts Small Enough to Trust
A practical reflection on designing data contracts that are narrow, testable, and stable enough for teams to rely on.
Writing
Blog
Deep-dives on software architecture and the way source code is structured — written to be understood by beginners, yet useful to teams shipping at scale. Diagrams, real examples, no hand-waving.
Latest articles — Page 2 of 23
Ways of Working
Keeping Checklists Close to the Work
A practical note on making checklists useful by placing them where people actually decide, review, release, and hand off work.
Perspectives & Field Notes
The Small Relief of a Reversible Decision
A reflective note on lowering decision stress by knowing which choices can be changed safely after new information arrives.
AI & The Future
Treating AI Suggestions as Draft Evidence
A practical reflection on using AI output as a starting point for investigation, not as a finished answer that replaces verification.
Engineering Culture
Making Space for the Quiet Reviewer
A calm note on helping quieter teammates contribute thoughtful review feedback without forcing every useful signal into the loudest channel.
Source & Architecture
Choosing Boring Boundaries on Purpose
A practical reflection on choosing simple software boundaries that make ownership, testing, and future change easier to reason about.
Ways of Working
Writing Status Updates People Can Act On
A practical note on writing status updates that tell readers what changed, what is blocked, and what action is needed next.
Perspectives & Field Notes
The Patience to Let Context Arrive
A reflective note on waiting long enough for missing context to surface before turning uncertainty into a decision.
AI & The Future
Keeping AI Changes Small Enough to Review
A practical reflection on using AI safely by keeping generated changes narrow, inspectable, and tied to evidence.