From beep to empty seat: the six levels of self-driving code

  • Reading time:16 mins read

Back in 2016 I bought a new car, and one afternoon on the motorway it did something that made the hair on my arms stand up.

I was driving home, traffic was light, and I clicked the thing on. And the car just… drove. It held the lane on its own. Gentle little corrections, left, right, following the curve of the road like it had done it a thousand times. My hands were still on the wheel — the car insisted on that, it would beep at me and sulk if I let go for too long — but they weren’t doing anything. They were just resting there. Almost useless.

I had been driving for twenty years at that point. Two decades of the thing being mine to do — the steering, the watching, the tiny constant negotiation between me and the road. And here was a machine, in my own car, doing it while I sat there like a passenger in my own life. It was wonderful. It was also a little bit terrifying, in the way that wonderful new things often are. I remember thinking: this is it, the floor shifted under me, and it didn’t even make a sound.

I didn’t know it back then, but I had just met Level 2.

Continue ReadingFrom beep to empty seat: the six levels of self-driving code

UBI won’t save us, and the nurse will tell you why

  • Reading time:7 mins read

I have a friend who is a nurse. Not the TV kind, with good lighting and a romance subplot. The real kind. She does twelve-hour shifts, she lifts grown men who cannot lift themselves, she cleans up things you and I would rather not put into words, and she holds the hand of someone who is dying while their family is stuck in traffic. Then she goes home, sleeps badly, and does it again. Nights, weekends, Christmas.

Lately everybody is telling me she is going to be fine. Because of UBI.

Continue ReadingUBI won’t save us, and the nurse will tell you why

The lump of labour fallacy fallacy

  • Reading time:9 mins read

Every time someone says the machines are coming for the jobs, there’s a guy in the back of the room who knows the term. Lump of labour fallacy. He’s read his economics and he’ll explain it to you slowly, the way you explain things to a child. Work isn’t a fixed pie, he says. Automate one job and the economy invents three more somewhere you couldn’t have predicted. It happened with the loom, it happened with the spreadsheet, it happened with the ATM – banks hired more tellers after the cash machine, not fewer, look it up. So relax. Every century the automation take the jobs, and every century we all somehow still have work.

He’s right. He’s been right for two hundred years.

That’s exactly what worries me.

Continue ReadingThe lump of labour fallacy fallacy

Your Object IDs Have No Excuse Now – Ninja Comes to CI/CD

  • Reading time:2 mins read

AL Object ID Ninja is now available as a GitHub Action and an Azure DevOps Pipeline Task. It scans your AL repository during CI/CD and fails the build if it finds any object IDs, field IDs, or enum value IDs that aren’t tracked by the Ninja backend. No more spreadsheets, no more “we’ll coordinate manually”, no more conflicts surfacing during deployment.

Multi-app repos and app pools are supported automatically.

Continue ReadingYour Object IDs Have No Excuse Now – Ninja Comes to CI/CD

Context Engineering – The Thing Almost Nobody Is Actually Talking About

  • Reading time:10 mins read

Today I want to talk about something that barely anyone is talking about. Context engineering.

We hear about prompts constantly. We hear about the latest model releases, the agentic frameworks, the AI-powered IDEs, the MCP servers (luckily we don’t hear about vibe coding all that much anymore). We hear about a lot of things. You name it – we hear about it.

But context engineering? Not so much.

And I find that strange, because if there is one lesson I have taken away from spending the past nine months writing code almost exclusively with AI agents (last six of which you can drop the “almost” word), it is this: context matters more than your prompt. Significantly more. Whenever my agents produced results that I could never match – faster, more consistent, undeniably better – every single time I could trace that back to one thing. Precise context.

That word, precise, is doing a lot of work in that sentence. Remember it.

Continue ReadingContext Engineering – The Thing Almost Nobody Is Actually Talking About

AL Object ID Ninja 3.2.1: A Lot Has Happened in Four Days

  • Reading time:8 mins read

I’ve been busy over weekend with completing a few work items that were in the cooking for a while. Some have been on my wish-list since day one, some have been brewing since a few years ago. It’s unbelievable how far certain architectural decisions can go, and I am genuinely excited to bring this new version to the daylight: 3.2.1.

So, 3-2-1 go!

Continue ReadingAL Object ID Ninja 3.2.1: A Lot Has Happened in Four Days

When GUIDs Collide: The App ID Problem Nobody Expected

  • Reading time:6 mins read

You know what’s supposed to be unique? Snowflakes. Fingerprints. And GUIDs.

A GUID (Globally Unique Identifier) is mathematically designed to be so astronomically unique that if you generated one hundred billion GUIDs per second, you’d still have a better chances of being struck by lightning twice and then winning the lottery, all on the same day, than generating a duplicate.

And yet, here we are. Talking about duplicate App IDs in Business Central.

Continue ReadingWhen GUIDs Collide: The App ID Problem Nobody Expected