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.
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 4 of 23
AI & The Future
Asking AI to Show Its Working Context
A practical reflection on asking AI systems to expose their working context so engineers can verify evidence, assumptions, and gaps.
Engineering Culture
Why Good Teams Make Risk Visible Early
A calm note on why healthy teams surface risk early: not to create fear, but to give the work more room to adjust.
Source & Architecture
Designing for the Change You Can Actually See
A practical reflection on designing software around visible change patterns instead of abstract future flexibility that may never arrive.
Ways of Working
Writing Next Steps That Actually Help
A practical note on writing next steps that are specific enough to move work forward: owner, action, evidence, and a useful stopping point.
Perspectives & Field Notes
A Calm Way to Carry Uncertainty
A reflective note on carrying uncertainty without letting it become avoidance: name it, bound it, assign it, and keep moving with care.
AI & The Future
Letting AI Draft While Humans Keep the Map
A practical reflection on using AI to draft faster while humans keep the system map: constraints, sources, ownership, and verification paths.
Engineering Culture
The Culture Hidden in Small Reviews
A calm note on how engineering culture shows up in small reviews: the phrasing, patience, and care teams bring to ordinary feedback.
Source & Architecture
When Boundaries Need Examples More Than Names
A practical reflection on why software boundaries become clearer when teams anchor them in examples, responsibilities, and behavior instead of only naming layers.