Ways of Working
Turning Review Evidence Into Team Memory
A practical note on converting review findings, commands, screenshots, and decisions into reusable team memory instead of one-time approval artifacts.
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.
Browse by topic
Source & Architecture
How to structure source code so it survives growth, teams, and change.
41 articlesEngineering Culture
The human side of building software — reviews, feedback, mentorship, and teams that grow people instead of burning them out.
41 articlesAI & The Future
Making sense of AI — from context engineering to building reliable, production-ready AI products.
41 articlesPerspectives & Field Notes
Personal reflections from work, learning, people, and the quiet moments that shape a career.
31 articlesWays of Working
How software teams actually operate and work together — from Agile and Scrum to how delivery really happens in big corps, startups, and outsourcing.
50 articlesLatest articles
Perspectives & Field Notes
What Thirty Days of Small Notes Can Teach
A reflective note on how a month of small daily observations can reveal patterns that are easy to miss in the middle of work.
AI & The Future
Letting AI Speed Up the Search, Not the Judgment
A practical reflection on using AI to broaden investigation while keeping source checking, trade-off decisions, and accountability with people.
Engineering Culture
Protecting Attention in a Busy Team
A calm note on treating attention as a shared team resource, not an infinite personal budget that people can recover alone.
Source & Architecture
Designing Defaults That Fail Safely
A practical reflection on choosing defaults that protect users and systems when configuration, rollout, or external dependency behavior is uncertain.
Ways of Working
Making Handoffs Honest About What Is Unknown
A practical note on writing handoffs that include open questions, assumptions, and risk instead of pretending the work is more certain than it is.
Perspectives & Field Notes
The Quiet Discipline of Finishing Properly
A reflective note on the small discipline of closing work with evidence, cleanup, and context instead of only reaching the visible finish line.
AI & The Future
Asking AI to Name Its Assumptions
A practical reflection on making AI-assisted work safer by asking the model to expose assumptions before accepting its answer.
Engineering Culture
Noticing Friction Before It Becomes Blame
A calm note on treating repeated team friction as useful signal before it hardens into personal blame.