Engineering

All on engineering.

Essays on engineering systems, delivery, architecture, and the operating models behind reliable work.

№ 01

Your sprint planning is missing a column

Story points measure human effort. In an AI-augmented codebase, the bigger cost is model compute. Why we're still planning like it's 2022.

↗︎
№ 02

I got my hands-on coding back, with a bonus

Years of architecture and management had dulled my implementation speed. Copilots didn't just close the gap - they restored the flow, with experience attached.

↗︎
№ 03

The two coding copilots are teammates, not a winner

Comparing Claude Sonnet and GPT-5 on daily engineering work. The answer isn't a ranking. It's a division of labour.

↗︎
№ 04

I built a small app on my coffee break

Yesterday I skipped the usual scroll, opened Lovable.dev, and built the small thing that automates one of my errands. It was the most relaxed I’ve been all week.

↗︎
№ 05

What AI copilots can - and cannot - do for engineering organisations

Notes from embedding generative-AI tooling across a software development lifecycle: what worked, what didn't, and what we learned not to measure.

↗︎
№ 06

"AI-first" is a verb, not a slogan

Every team I've ever seen succeed with AI treats it as a verb - a practice applied to specific workflows - not a banner hung over the whole company.

↗︎
№ 07

Which language should I learn? The question beneath the question

The 'JavaScript for everything' joke lands because it's nearly true. The real question is what you're trying to build, and the answer has changed since 2020.

↗︎
№ 08

Are we re-solving live broadcast - or solving a different problem?

Broadcast TV solved one-to-many at scale 75 years ago. Streaming engineers keep re-solving similar-looking problems. The case for streaming is real but narrower than its enthusiasts claim.

↗︎