May 29, 2026
Ctrl-Alt-Delete Your Brain?
We should be more tired than the model
Coders say AI makes them feel productive while their brains quietly clock out
TLDR: A programmer argued that relying too much on AI can make you feel productive without truly learning, so they’re adding friction back into their work on purpose. Commenters were split between “use it as a tutor” and “this is just the road to burnout and weaker skills,” which is why the debate hit such a nerve.
A fresh developer confessional has set off a very relatable panic: what if using AI to write code makes you look busy while your brain takes the day off? The post argues that these tools can leave people with the feeling of having built something, without the messy mental struggle that usually helps ideas stick. The proposed cure is almost scandalously old-school: slow down, write more by hand, ask questions, read the real docs, and yes, even get tired on purpose. In other words, if the machine is doing all the sweating, maybe you’re not actually learning much.
And the comments? Absolute developer group therapy with a side of doom. One camp nodded furiously and said they already use AI like a study buddy, not a magic answer box. Aldipower basically waved the “read the actual manual” flag, saying they’d rather have the bot point them to real sources than spoon-feed a summary. Others admitted the temptation is brutal: stantonius said the real effort now is not doing the work, but resisting the one-click shortcut before your own code starts looking alien.
Then came the darker turn. Sam-cop-vimes saw a bigger nightmare lurking here: if workers are expected to produce more with AI, “be more tired than the model” starts sounding less like wisdom and more like a burnout slogan. Meanwhile, another mini-revolt broke out over the whole chat-box setup itself, with one commenter comparing modern AI coding tools to a slot machine in markdown clothing. The vibe: half self-help, half existential crisis, with everyone wondering whether they’re learning faster—or just gambling with their own skills.
Key Points
- •The article says agentic code-generation sessions can leave developers with produced code but less of the internal understanding associated with writing code manually.
- •The author explains coding work through short-term, working, and long-term memory, arguing these processes normally operate together when programmers read and write code.
- •The article states that default code-generation workflows are unfavorable to skill retention because they provide rapid solutions with minimal cognitive effort.
- •The author reports adopting a more deliberate workflow, including writing initial implementations manually and using AI primarily for review, questioning, and comparison of approaches.
- •The article concludes that adding friction to AI-assisted development may reduce short-term speed gains while improving long-term understanding and tool use.