There's a version of this future everyone is quietly chasing. The agent drives, fully, and you just watch. You hand it the repo, you hand it the goal, and you go get coffee. Total delegation.
Honestly, it's the biggest trap in the whole thing.
Not because the agent can't do the work. It usually can. The trap springs later, at the exact moment it can't. Something breaks. The build is red, the behavior is wrong, and the model is confidently going in circles. Now it's your problem. And if you never understood what it built, you're not debugging anything. You're digging through a stranger's code with no map and no memory of how it got there.
Think about how a junior developer actually works. They take the task, they run at it, and when they hit a wall they can't get over, they escalate. To you. That's the deal. You're the floor they land on.
So here's the uncomfortable question. When the agent escalates, and it will, who is your floor?
There isn't one. You are it. If you're stuck too, the whole thing just stops, and no clever prompt is getting you out. The agent gets to be the junior. You don't get to be a second junior standing next to it, shrugging.
That quietly flips the question I see everyone asking. It's not "how much can I hand off." It's "what is the minimum I have to keep understanding so I can catch the thing when it falls through."
Not every line. You don't need to hold all of it in your head, that's the whole point of delegating. But there is a floor, and it's built out of the load-bearing stuff. How the data actually moves through the system. Where the state lives. What the critical path is. The seams where the pieces talk to each other. The one or two decisions everything else leans on.
The test I use is pretty simple. Can I trace a single request from start to finish and explain it out loud? When something goes wrong, can I make a real guess about where it went wrong, instead of just pasting the error back into the model and praying? If the answer is yes, I'm happy to let it run, and I can grab the wheel the moment it drifts. If the answer is no, I don't really own this system. I'm renting it from an agent that might not pick up the phone next time.
So let the agent drive. Seriously, that's where the speed is. Just keep your hands on the load-bearing walls. Read the parts that would be expensive to get wrong. Stay fluent in the skeleton even while you hand off the flesh.
Because the goal was never to stop understanding your own system. It was to stop doing the parts that don't need you, while staying the one person who can always find the part that does.
Takeaway: You can delegate the typing. You can't delegate being the last line of defense. Know the skeleton, or you don't really own the system.
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.