A PhD student says Claude Code eroded their debugging instinct

A third-year NLP PhD student traced how far they'd delegated to Claude Code, in a post that topped r/MachineLearning on August 31. It started small: argparse boilerplate, then plotting code. Then it kept going. Experiment scaffolding, dataloader refactors, first-pass debugging on training runs, analysis scripts. Their job narrowed to reading diffs and approving them.

Throughput went up. That's the trade everyone points to. What they noticed is the other side of it: they no longer hold their own codebase in their head. When a result looks off now, they hunt through the code like it belongs to someone else, reasoning backward from the numbers instead of forward from what they know the code does. Bugs surface later than they used to.

That trade is real for anyone using these tools daily. The convenience shows up immediately. The cost doesn't show up until the moment you need instinct you didn't build.

I watch for the same thing in my own work. Writing something by hand now and then is the only check I've found, and it's not a fix, just a way to notice the drift before it gets expensive. The post doesn't say whether the student has changed how they work since noticing it, only that they noticed.