Engineering Culture
What Calm Ownership Looks Like in Practice
A grounded note on ownership as clear follow-through, explicit handoffs, and steady accountability without drama.
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 3 of 23
Source & Architecture
Designing With Escape Hatches, Not Back Doors
A practical reflection on building safe operational escape hatches that are explicit, audited, and bounded instead of hidden back doors.
Ways of Working
Closing the Loop Before Starting the Next One
A practical note on closing work loops with evidence, decisions, and handoff context before the team rushes into the next task.
Perspectives & Field Notes
When Progress Feels Like Removing Weight
A reflective note on the kind of progress that comes from reducing load, clearing ambiguity, and making the next step lighter.
AI & The Future
Letting AI Draft the Boring First Pass
A practical reflection on using AI for the plain first draft, while keeping human judgment focused on evidence, shape, and responsibility.
Engineering Culture
The Quiet Skill of Asking for Help Early
A calm note on why asking for help early is not weakness, but one of the small habits that keeps work honest and teams healthy.
Source & Architecture
Making Interfaces Honest About System Limits
A practical reflection on designing interfaces that show real system limits before users and operators have to discover them through failure.
Ways of Working
Keeping Meeting Notes Close to Decisions
A practical note on keeping meeting notes close to decisions so future teammates can find context, trade-offs, and follow-through without replaying the meeting.
Perspectives & Field Notes
The Relief of a Well-Named Problem
A reflective note on how a well-named problem reduces tension by turning scattered discomfort into something people can examine together.