From the Commodore 64 to Cloud Systems
A sample personal-history structure showing how a lifelong builder’s perspective can connect early home computers with modern software practice.
Read blog postBlog post index
Latest writing · Page 2
Practical notes from decades of building software, teams, and companies.
Latest blog posts
Follow via RSS
What Still Matters After the Framework Changes
A practical sample essay about separating durable software design from the replaceable conventions of any particular framework.
Read blog post
Guardrails That Let Coding Agents Move Faster
A sample engineering workflow for giving coding agents useful autonomy through explicit scope, permissions, evidence, and recovery paths.
Read blog post
The Hidden Cost of Just One More Service
A sample architecture analysis of the operational, organizational, and exit costs concealed behind a seemingly small service dependency.
Read blog post
Architecture Reviews Should End with a Decision
A sample leadership guide to architecture reviews that expose trade-offs, assign ownership, and produce a usable record instead of ceremony.
Read blog post
What to Measure Before Product-Market Fit
A sample founder’s guide to evidence that reduces product uncertainty before dashboards and growth metrics become persuasive distractions.
Read blog post
The Management Work Inside a Technical Migration
A sample engineering-leadership essay about sequencing ownership, communication, risk, and learning alongside the code of a major migration.
Read blog post
Good Incident Reviews Change the System
A sample reliability essay about turning incident evidence into stronger controls, clearer ownership, and safer operating conditions without blame.
Read blog post
Work with AI Without Outsourcing Your Judgment
A sample field guide to using AI for leverage while keeping problem framing, trade-offs, verification, and accountability in human hands.
Read blog post
Sustainable Pace Is an Engineering Constraint
A sample leadership essay about designing workload, feedback, and recovery so teams can produce reliable software beyond a single deadline.
Read blog post