thisFeelingNeverGoesAway: the title comforts; the comments audit what’s left
Source: thisFeelingNeverGoesAway (r/ProgrammerHumor, ~8,917 upvotes / 113 comments)
Another programmer meme: thisFeelingNeverGoesAway — the crash-and-rush of teaching a kid to code, or debugging yourself until it finally compiles. The feeling, the title promises, never leaves.
The comments barely unpack the joke. The top line is colder:
Then his son discovers AI. (+448)
Right under it, a long sad take (+316): no kid will really feel that again — the maddening random segfault, then the jolt when it finally builds after hours line by line. You can still refuse AI on purpose. That is no longer the default path.
Three fights in the thread
1. AI stole the clear
“Claude stole from us.” Someone is 10× more efficient and feels 1/10 the joy; aha moments have to be hunted elsewhere at work. Darker take: coding becomes knitting — hobbyists remain, industry moves on; the next generation looks more like QA.
2. Autopsy of the Stack Overflow era
“What if he discovers Stack Overflow first? THEY TELL ME I’M WRONG!” (+219)
Duplicates, Needs More Focus, closed questions — the old rites. Someone cites the June 2026 figure: monthly SO questions down 99%+ from the 2014 peak. A chatbot trained on SO still opens with: “We’re not here to do your homework.”
3. The debug loop isn’t dead yet
“Wait, why does this work?!” (+145)
Remove “useless” code and it breaks; put it back and it still breaks; fix it and realize it never should have worked — someone lived that three minutes ago. Punch cards didn’t generalize. Debugging as investigating unexpected behavior probably does, as long as software is written.
A minority bets on kids who insist on learning like Dennis Ritchie, no LLM; and on “code guys,” the way car guys remain after most owners stopped wrenching.
Same thesis as “accelerate thinking vs replace it”
Three months ago I wrote AI panic: is human intelligence locked in?, drawing on a 30-year game developer’s Reddit essay and two V2EX threads about effort feeling illegitimate and “the programmer industry feels dead.”
The point was not “don’t use AI.” It was:
The real split is not whether you use AI, but whether you use it to accelerate thinking or to replace thinking.
Today’s meme thread maps almost line for line:
| This meme thread | That earlier essay |
|---|---|
| 10× output, 1/10 joy | “No fun, no achievement — all credit goes to AI” |
| Kids never get the segfault clear | “Juniors become meat proxies for AI and learn nothing” |
| SO / Claude short-circuit the struggle | “AI boosts confidence; you don’t notice you stopped learning” |
| Debugging still transfers vs becomes knitting | Can you still judge, restate, and locate faults yourself? |
So: the title comforts (feeling never goes away); the comments audit (how much feeling is left). The audit uses the same ruler as accelerate-vs-replace.
One more link: What can programmers still do argued that value shifts to judgment, domain, and responsibility. When typing code no longer pays enough achievement feedback, you have to reconnect the loop to the parts where you still think — or joy and skill thin out together.
An unsappy close
The title can keep saying never goes away — the WTF loop is still real. The default path changed: stuck → ask the model → paste → continue is much shorter than stuck → read docs → try line by line.
Short is not the crime. The crime is no longer being able to say why it worked, where the next stuck will be, and who owns the failure.
Best read of the meme is not nostalgia. It is a checklist:
- Was your last aha earned, or handed to you?
- Without the chat log, can you restate the plan?
- When mentoring, is it “explain before merge” or “ships if it runs”?
The feeling will not vanish overnight. It thins quietly. When it thins, the useful question is still the old one — am I accelerating thinking, or replacing it?
Comments