In my last post I described how we structure delivery so that human judgement is spent where it matters, and I left one problem open: that model assumes seasoned judgement at the gates, and I could not say how a junior grows it inside a system that shields them from the grind that used to build it.

I still would not call it solved. AI-native is a young way of working, and, as far as I know, nobody has grown a whole cohort of engineers inside it yet. But I am confident in the approach, because most of it was already there in how juniors learnt the craft before any of this existed. This is where my thinking stands today.<br>' name=description>How juniors learn the trade when an agent writes the code

' data-copy-icon='<br>' id=copy-cfg style=display:none><br>How juniors learn the trade when an agent writes the code<br>Aug 21, 2026

In my last post I described how we structure delivery so that human judgement is spent where it matters, and I left one problem open: that model assumes seasoned judgement at the gates, and I could not say how a junior grows it inside a system that shields them from the grind that used to build it.I still would not call it solved. AI-native is a young way of working, and, as far as I know, nobody has grown a whole cohort of engineers inside it yet. But I am confident in the approach, because most of it was already there in how juniors learnt the craft before any of this existed. This is where my thinking stands today.<br>The mechanic is older than it looks<br>Juniors never learnt the trade by inventing everything from scratch. For the last fifteen years a large part of the job was reading: Stack Overflow, a library's source, a colleague's pull request. The snippet was rarely the hard part. The hard part was deciding whether it was correct for the problem actually in front of you, and what it would cost you in six months.How much a junior learnt from that depended on how much they put in. Copy, paste, run, move on taught nothing; the code worked, or it did not, and the engineer was no wiser. Design was the same story. Most juniors mimicked whatever the codebase already did. The ones who grew asked why the pattern had been chosen in the first place, and noticed when it did not fit their case.An AI agent is the same mechanic with the friction removed. Pressing enter until the tests go green is copy-paste without reading, at a hundred times the volume. Accepting whatever structure the agent proposes is mimicking the codebase without asking why, except that now the agent does the mimicking too. The result is familiar: working code, and an engineer no wiser for it.I have watched it happen with juniors I coached through the arrival of these tools. One junior turned in an IPv4 and IPv6 parser with subnet and mask matching, several hundred lines, neat and complete. They could walk me through parts of it, but not why we were writing our own parser at all, nor what most of those lines were for. It was plainly agent work. A few questions in, they saw it themselves: the understanding was too shallow to justify the implementation, and once we read it together, it had bugs. That conversation, and what came out of it, is the loop later in this post, in miniature.What has changed is that the mistakes got quieter. A Stack Overflow snippet that did not fit your problem usually failed loudly. An agent's implementation that does not fit your problem passes every test and is wrong in the one edge case that matters. The reading was always the job. Writing the code by hand used to force a minimum of it on you; now nothing does, and it is the one part of the job the agent cannot do for you: it can review the code, it cannot understand it on your behalf.There is one thing reading never gave a junior. Writing the code yourself meant being wrong in public, quickly: the build broke, the test failed, the design collapsed under the first real use, and you learnt what your mental model had missed. Agent code that passes every test carries no such signal, so any answer to how juniors learn now has to say where that feedback comes from. Mine is in the human loop below.It is not only a junior problem<br>I should say where my evidence comes from. I have coached juniors through every generation of these tools since the first Copilot, and experienced engineers into working this way before the structure in the previous post existed.The pattern was clearest in the experienced engineers. Engineers with a decade or more of reading code behind them, who would never have approved a colleague's PR unread, quietly stopped reading the agent's. The output looked right and the tests were green, so the habit went. Some of them stopped one step further upstream and let the agent make the design call as well, then defended it in review without being able to say why it was the right one.One of the most experienced voices in our community says he does not read the agent's code at all. Uncle Bob Martin, who started coding in the late sixties, wrote...