One observation, followed until it resolves.
Field notes on product complexity, team structure, and how systems slow down as they scale. Published here first. Cross-posted to Medium and mentioned in the Core and Bloat newsletter.
He Did Nothing Wrong. I Still Had to Start Over.
I was the one sent to the company's biggest customers, to fix the things in their own systems the product could not reach. Token ring, coax, a bank of modems. All of it is gone now. That was always the job.
Read the note →
How I Run a Full CTO Workload From a Bag That Fits in Any Cabin
Three machines, multiple fallbacks, and the trade-offs I live with.
Read the note →
What AI Asks of Us, What the Machine Asked of Her
Every machine since has made the same offer. It carries more, and you pay by changing how you work.
Read the note →
I Treated It as a Tuesday
Sometimes the best argument wins. More often, the one that wins is the one still being made when the decision forms.
Read the note →
He Was Defending Us Against a World That No Longer Existed
Legacy is not in the code. Legacy is in people.
Read the note →
I Fly for Budget Meetings. I Do Not Fly to Write Architecture.
A decision produces presence. A policy produces attendance.
Read the note →
From Mainframes to Motorbikes: A CTO's Journey Building Tech and Leading Teams
I started on Unix mainframes when the internet was still a curiosity. What followed was thirty-five years of building systems and leading teams. Until Bangkok, a motorbike, and a clearer sense of what actually matters.
Read the note →The originals live here. Also distributed on Medium.