Ways of Working
The Calm Way to Handle Scope Changes
A practical note on scope changes: how teams can discuss new work calmly by making trade-offs visible, protecting focus, and changing plans without blame.
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 6 of 23
Perspectives & Field Notes
Why Quiet Consistency Compounds
A calm reflection on quiet consistency: why small repeated returns to a craft, relationship, codebase, or habit often become visible long after the effort begins.
AI & The Future
AI Tools for Reading a Codebase
A practical guide to using AI tools while reading a codebase: where summaries help, where they mislead, and how engineers can combine AI assistance with source-level verification.
Engineering Culture
The Reviewer as a Future Reader
A reflective note on code review culture: how treating the reviewer as a future reader can make pull requests clearer, kinder, and more useful for the people who will maintain the change later.
Source & Architecture
Refactoring Toward a Clearer Core
A practical reflection on refactoring toward a clearer core: how teams can reduce coupling, protect behavior, and make the center of a codebase easier for future teammates to understand.
Ways of Working
Managing Dependencies Without Blame
A practical note on delivery dependencies: how teams can make blockers visible early, coordinate calmly, and avoid turning normal coupling into personal blame.
Perspectives & Field Notes
The Difference Between Confidence and Evidence
A reflective field note on why confidence becomes useful only when it is tied to evidence, and how teams can keep conviction without losing humility.
AI & The Future
From Prototype Demo to Production Behavior
A grounded AI product note on the gap between an impressive prototype demo and the production behavior users can safely depend on.
Engineering Culture
When Silence in a Team Becomes a Signal
A calm look at team silence: how quiet rooms, missing replies, and low participation can reveal unclear ownership, unsafe disagreement, fatigue, or hidden context.