A final-year software engineering student says Claude does the thinking and he cannot tell what he knows

“My default reaction to literally any roadblock is to alt-tab and open Claude.” A software engineering student in his final year wrote that on r/ClaudeAI, under a post asking whether he is actually learning anything.

The progression he describes

It started small. Paste an error log. Ask about a strange JVM exception. Generate a quick regular expression.

Then it grew: “refactor this controller.” Now it is full delivery. He outlines the requirements, Claude plans the architecture, and the model writes the implementation.

His own summary of where that leaves him: “The gap between ‘I can make this run’ and ‘I actually understand how this runs’ is getting dangerous.” He says he is starting to panic about his baseline competence with a degree months away.

The mechanism, not the tool

The interesting part of the post is not the confession, it is the account of how it happened without a decision being made.

Learning to program has historically been enforced by friction. Reading documentation because nothing else explains the API. Sitting with a stack trace because there is no one to hand it to. Rebuilding something badly, twice. The tooling is now good enough to remove exactly that friction, and it removes it invitingly, one small request at a time.

A course project that runs perfectly proves the project runs. It says nothing about whether its author could reconstruct the design on a whiteboard, and coursework is not usually assessed on that difference.

An entire graduating cohort is about to discover which side of the gap it is on, in interviews built specifically to test the part the tooling covered.