We’re about to learn a painful lesson about delayed gratification in software engineering.
New data tracked 26,811 students from January 2023 through June 2025. Students using AI for homework saw their scores jump. Completion time dropped nearly half. They aced the assignments.
Then exam season came. Those same students scored significantly worse when they couldn’t use the tool.
The homework phase is over. The exam phase is coming.
We’re doing this in software right now. Vibe coding feels incredible. Features ship fast. Demos land. Stakeholders cheer. Nobody’s asking what happens in Month 18 when the original dev has left and nobody understands the codebase.
The Autopilot Problem
Commercial pilots fly with autopilot for most of every flight. They’re required to maintain manual flying proficiency regardless. If the system fails mid-air and the pilot can’t take over, people die.
Most teams using AI right now have forgotten how to fly manually. They’ve become passengers in their own systems. The autopilot flies, nobody checks instruments, and the first sign of trouble will be a breach notice or outage.
Three Rules
Command the mission. Define architecture before prompting. Ambiguity kills in code and in flight.
Delegate selectively. Offload mechanical work. Keep design and security reviews human.
Verify everything. Audit before production. Never trust the automation without checking instruments.
The Bill Comes Due
Quick wins feel good. Sustainable engineering feels boring. Boring keeps systems standing.
Organisations surviving the next two years won’t be the ones that shipped fastest. They’ll be the ones who remember how to fly without the aids.
The students who leaned on AI for homework are walking into exams right now. Our codebases are walking into theirs.
Same lesson. Same outcome. Unless we change the approach.
HOTAS. Full stop.