Picture the sharpest assistant you can imagine — and put them in a locked room with no windows. They can reason about anything, but only about what you hand through the door. AI is exactly that: brilliant, and blind. It knows nothing about your business, your customers, or your week except what you show it. So before any judgment happens, something has to gather the right information and carry it in. That carrying is a coding job — and it's the part that used to stop you cold.
It helps to see where judgment actually sits. It's not the whole system — it's one layer, resting on top of two others:
Data is the foundation under the AI. But code is the foundation under the data — and that bottom layer is the one that just came within your reach.
Your data is scattered on purpose
Think about where the facts of your work actually live. Some sit in email, some in your billing system, some in spreadsheets, some locked inside an app with its own front desk. None of it sits together, because every app was built to keep its own corner and rarely hand it over. For a person, pulling it into one place means hours of copy-paste. For an AI, it isn't even an option until the data's been gathered — it can't reason about a number it was never shown.
So the first move, every time, is the unglamorous one: go collect the scattered pieces and lay them out somewhere tidy. Nothing clever happens until that's done.
Gathering it is code — and that's the part that's new
Reaching into all those places and pulling the data into one organized spot is itself a small program. It's the quiet half of every AI system — unglamorous, and the reason these things were hard to build in the first place. Here's what changed: you can now describe that gathering in plain English and have a coding agent write the program for you. The hard part was never the AI being smart enough; it was getting it something to look at. That's the part that just opened up.
And it doesn't end once the AI decides. A decision is just words until something acts on it — flags the account, sends the note, files the ticket, adds the row. That's code again, on the far side of the judgment. So a real AI system is a kind of sandwich:
Your data, spread across email, apps, and spreadsheets
A program collects it into one tidy place
Reads it and makes the call
Does something with the answer
Judgment is the thin, exciting layer in the middle. The code on both sides is ordinary programming — and without it, there's no sandwich.
The foundation under the foundation
You'll hear that data is the foundation of AI, and that's true — no data, nothing to judge. But go one layer deeper. The data doesn't gather itself. Getting it out of all those scattered corners and in front of the AI takes code — and code is the thing you can now write just by describing what you want. So yes, data is the foundation of AI. And coding agents are the foundation of the data.
That's why the judgment layer, exciting as it is, was never the real story. The real story is the bottom of the stack: the part that puts any of this within reach is finally yours. Once you can build the thing that feeds it, the choice of what to build — a plain program, a layer of judgment, or both — is yours too. More on that judgment layer →