Vector · every second Tuesday
One Vector a fortnight. No hype, no spam.
Stories from the cockpit and the codebase about staying useful as AI changes the job. Written by me, not a content team.
What a Vector is
In the cockpit, a vector is a heading. Air traffic control gives you one, you fly it, and you hold it until the next one comes. Each Vector is one of those: a single long-form piece, about ten minutes' reading, on one idea about how software people stay valuable, and human, when AI writes the code.
What you'll get
- One Vector every second Tuesday. The whole piece is in the email. No teasers, no "read more".
- A story first. A flight, a binder, a cutover weekend. Then what it taught me, and what I'd do with it this week.
- Opinions from someone still shipping. Engineering leadership, AI in real businesses, and predictable delivery over raw speed.
- A reply address that reaches me. I read every reply, and plenty of Vectors start as one.
What you won't get
No daily emails, no sponsors, no hype words, and nobody selling you a course. If I write about something I'm building, I'll say so plainly.
If you'd rather sample first, the back catalogue is below and on the Writing page. Vector 01 is the place to start.
Sent so far
All Vectors →-
Vector 03 ·
Your juniors aren't learning
The code reviews that made me a developer, and what happens to the next generation when AI does all the reps.
-
Vector 02 ·
The plan is not the outcome
What pilots learned about automation complacency, and why rubber-stamping AI pull requests is the same trap.
-
Vector 01 ·
How I've (somehow) stayed useful through every disruption
From a 747 over the school gate to a needle tuned to 540. Five turning points, and what they taught me about staying useful when the tools keep changing.