The situation
The first afternoon goes absurdly well. You describe something, it appears, it runs. A week later the same tool is confidently rewriting a part that already worked, the fix for one thing quietly breaks another, and you cannot tell whether you are asking badly or asking for something it cannot do. Meanwhile you keep reading that this replaces an entire engineering department.
The idea in one paragraph
These tools are very good at producing code for a job somebody has already decided on and described clearly. They are weaker at holding a whole system in mind at once, and they do not decide what is worth building. Only the first of those three jobs has been automated. So the limit you run into is not how well you type: it is how much of a project one person can personally hold, decide about and check. Better tools raise that limit. They do not remove it.
What one person holds, and what an organisation holds
| The work | One person with an AI coding tool | An organisation |
|---|---|---|
| Producing the code | Fast, and still getting faster | Also fast now |
| Knowing what the code should do | One head, one memory | Written down, argued over, revised |
| Deciding what is worth building | Your judgment, unassisted | Several roles disagreeing in a room |
| Remembering why a past choice was made | Only what you wrote down | Documents, reviews, people who were there |
| Being awake when it breaks at 3am | You | A rota |
Only the first row got automated. Every row below it is still staffed by exactly one person.
How it actually works
The tool works from the text in front of it and produces the most plausible continuation. Everything it appears to know about your project arrived during this session: files it opened, output it read, things you told it. It holds no independent memory of your intentions and has no stake in whether the thing is worth building at all.
That gives a clean dividing line. The parts of the job you can fully describe are the parts it can take. The parts you cannot describe, because they are still only in your head or in nobody's head yet, stay with you regardless of which model you use.
The same dividing line is why an enterprise is not a scope problem. A large company is not a large pile of code. It is many people holding different parts of one intention and keeping them aligned through meetings, documents and review. Give one person a very fast code producer and you have one person with a very fast code producer.
What this changes for you
- Choose projects whose whole shape fits in your head. That is the real size limit, not the line count.
- Decide what "done" means, in writing, before you ask for the work. That half is yours; the tool cannot supply it and will not ask for it.
- When a session starts going backwards, make the request smaller rather than louder. Repeating an oversized ask in firmer words almost never rescues it.
Where it breaks
This page is a snapshot, checked on 10 August 2026, and the line it draws moves. Assume the producing half keeps getting better and check the claim rather than trusting this page in a year.
The ceiling is also not a wall. One person can and does ship real products this way. What fails is expecting the tool to supply the judgment: what to build, what "correct" means here, what is safe to change. The opposite failure is just as common, and just as expensive: deciding the tools are useless because one long session went badly, when the honest reading was that the ask was too big to hold.
Terms used on this page
- AI coding tool — a program that can read your project files, write code into them and, in some forms, run commands. Different from a chat window you paste code into.
- Session — one continuous conversation with the tool, from opening it to closing it. What it knows resets when you start a new one.
- Scope — the boundary of what you are asking for right now: what is included, and what is deliberately left out.
- Solo-operator ceiling — the limit set by how much of a project one person can hold, decide about and verify, rather than by how fast code can be produced.
Read next
What this costs — the two ways of paying for these tools, the limit you cannot see, and where the money actually goes, with the date every figure was checked.