Machine Collaboration Has Created a New Form of Writing, Perhaps
I’ve been building software and teams for close to twenty years — running an agency, leading engineering teams at The New York Times, and now working as CTO at an AI startup. That work leaves you with opinions about what actually works, what fails predictably, and which advice is detached from reality.
Until recently, I was too busy building to write about it. What changed is the process. Writing can now be iterative and collaborative, with machine intelligence in the loop. That collaboration has improved enough to change how thinking gets onto the page. This blog is an experiment in exploring what that enables — and where it fails — in practice.
I’ll write from direct experience, focusing on four areas. AI in practice: building and operating AI systems in the real world — tooling, tradeoffs, failure modes, no hype. Engineering leadership: how teams ship, how they don’t, and why — hiring, incentives, culture, and management. Growth engineering: treating growth as an engineering problem with experimentation, systems, and constraints. The startup CTO role: what the job actually looks like at an early-stage company, and how it differs from larger organisations.
No comments. If something here needs correction or extension, open an issue or submit a PR.