Matt Pocock, a self-taught developer who says he stopped writing code by hand around the release of Opus 4.5 in December 2025, argues the highest-leverage skill in the AI era is communication: being able to surface your unknown unknowns and tell an agent exactly what you care about. He claims the environment agents work in (a clean, testable, verifiable code base) matters far more than which model or harness you pick, and tells the story of abandoning spec-driven development after months of watching his code quality degrade. His practical advice: climb a "trust ladder" slowly, give agents your boring work rather than your most ambitious tasks, and run models at lower effort levels than most people do.
- Pocock treats the Opus 4.5 release in December 2025 as the threshold where he decided he would never write a line of code himself again; before that, agents hadn't clicked for him despite a decade of coding.
- He argues the biggest constraint isn't model intelligence but the communication gap between human and agent — the agent never knows what you care about unless you repeatedly tell it, so garbage environments produce garbage output.
- Old software engineering books about tests, checks and preventing classes of bugs "feel like they were written last week" because raising the floor for 100 mediocre human coders is the same problem as raising the floor for agents.
- His 'grill me' skill makes the agent interview him relentlessly before building, specifically to flush out unknown unknowns like security or deployment concerns the agent would otherwise invent answers for.
- He recommends domain-driven design's 'ubiquitous language' — the same terms in code, database, UI, and client conversations — and built a 'grill with docs' variant of his skill to construct that vocabulary.
- He tried spec-driven development for months on his custom video editor project after seeing an OpenAI talk claiming 'specs are the new code,' watched the code get steadily worse, and ditched specs to focus on code quality instead.
- Contrary hot take on effort levels: he runs Opus 5.5 at medium and is considering going lower, because his tests and code base do the quality work, giving him better token efficiency and speed.
- He disagrees with the 'give it your most ambitious task' pitch from AI lab leaders — he gets the most value giving agents menial, verifiable work he can easily check and correct.
- He reports 200-300 commits a day versus roughly 20 on a good day before agents, and says fixing his project so an agent could click through the app in a browser and take screenshots produced a bigger quality jump than any model upgrade.
A concrete, months-long failure against a popular industry idea, with the reasoning that replaced it: code is the environment the agent lives in.
I tried this for months because I thought this guy was OpenAI, right? He knows what he's talking about... And it wasn't working. So, I realized, no, I'm going to ditch these specs. I'm actually going to focus more on the code.
A direct rebuttal to the 'try your hardest task on our model' marketing line from AI lab leaders, grounded in how he actually uses agents day to day.
I don't know cuz I think the opposite, right? I think give it your most menial boring work... give it simple achievable tasks where you can measure the output and measure how good it is.
The best way to get the best work out of agents is to tell them what you care about.
The skill is being aware of unknown unknowns — of knowing that you could be missing things in your design and not trusting that you've come up with a complete design.
When you learn to drive, what's the first pedal you learn? You learn the brake. You learn how to stop.
What I'm excited about right now is turning agents into that annoying developer who's always on the team who says, 'No, we should do it the right way, not the fast way.'