On August 18, 2026, a programmer using the handle ramesh31 posted a question on Hacker News: *Does anyone else feel like everything is pointless now?*
He laid out his ledger of despair: New software releases? Who cares. Learning new computer science concepts? Whatever. Preparing for interviews? That job may not exist in a year. Side projects? They just add another shovel of dirt to the AI slop mountain—and the guy bagging groceries at the supermarket could do it with AI too. Everything is "done and cooked with AI" now.
He closed with a metaphor the entire thread kept chewing on:
> "It's like using cheat codes in a game. You can technically do everything, but nothing means anything anymore. The whole point and joy of our lives has been taken."
The post earned 297 upvotes and 175 comments. The day before, another post had asked whether this is the worst time in history to be a human, and commenters relayed the same cheat-code metaphor between the two threads. This wasn't one person's late-night breakdown—it was a shared public mood. A darkly comic detail: the post was removed from the front page at 116 points, yet the comment section burned all day. As someone noted bitterly, it had clearly hit a nerve.
Scrolling back through ramesh31's posting history reveals a complete anxiety trajectory: in 2022 he asked whether self-taught developers fear interviews; in February 2025 he asked what interviews look like now that everyone uses AI—that one got 535 upvotes. Over four years, his question drifted from "Am I good enough?" to "Does this even exist anymore?"
I read all 175 comments. The takeaway: there was no debate here, only the reflections of three kinds of lives in the same well.
1. The Person Who Wins Chess With an Engine
Commenter bah9 wrote a highly upvoted passage:
> "Coding to me is chess, and AI is the chess engine. Of course I care about winning—shipping products—but the game is being played by the engine, so winning brings no joy. Strangely many people don't get this. Apparently 90% of programmers hate chess; they only love winning. The sad part is now every 'bag boy' can win too—so what exactly is your value?"
Hidden in this passage is a distinction he may not have consciously made: *playing chess* and *winning* are two different things. The engine killed the latter. Someone followed up: the worst part is that now everyone thinks they're Carlsen.
Another commenter, frankie_t, twisted the cheat-code metaphor in a different direction. The problem isn't "I got the cheat code," he said—it's "a cheater entered the arena." The game itself is no longer worth playing seriously. Two different pains: one is my ability being diluted; the other is the rules being broken. Eerily, they lead to the same emptiness.
2. The Person Who Finally Finishes Projects
A 40-year-old frontend engineer, thatmiki, arrived and said he completely understood the original poster—then pivoted:
> "On personal projects—I'm actually *finishing things*! The joy of creation hasn't vanished; it changed. I miss the puzzle-solving moments too, but seeing my ideas become real, useful, and polished is deeply satisfying."
He added a line more informative than all the complaints in the thread combined: without his twenty years of frontend skill and UX judgment, these projects "would be way more slop."
Commenter throw-the-towel told a more vivid story. One night he stayed up until 3:30 a.m. hand-writing a CLI tool that converts shapefiles to vector tiles; two nights in, it still wasn't done. Opus would take about five minutes. His closing line:
> "The robot being better at eating cheese doesn't stop me from eating cheese."
3. The People Who Say "Reality Has No Cheat Codes"
Commenter chr15m dismantled the metaphor directly: "Life has no cheat codes. Physics still applies, and reality has an astonishing amount of detail." As soon as you start building things, you discover "anything is possible" doesn't hold—the boundary is exactly where the limits and the frontier are, and that's where the fun lives.
Someone offered a work example: point an agent at genuinely high-stakes ops, like coordinating TLS termination migration plus DNS changes for thousands of customers (many Fortune 500), and "it blows up after the first context compaction. Every time."
The requirements remain, the incidents remain, the edge cases remain—and they've never sympathized with anyone.
The most interesting comment came from Balgair, who claimed to be the very "bag boy" from the original post:
> "I'm more like the bagging guy in the post. AI is, for me, finally having a tool. The world has opened up now. I can build websites; I can do the things I always wanted to do with computers. Your world is finally open to me."
The same fact, reflecting two different lives. That line deserves to close every analysis of AI anxiety.
Psychology Answered This Years Ago
The real puzzle: what exactly is this "emptiness after cheating"?
Psychology delivered its verdict back in 2018. In that year's review of the *effort paradox*, Michael Inzlicht of the University of Toronto and colleagues wrote a sentence that reads like a letter mailed eight years early to ramesh31:
> "When zero-effort alternatives are readily available and apparent, exerting effort itself feels meaningless."
The brutal part: the devaluation doesn't require you to actually use the zero-effort option. Its mere existence dilutes your effort. This explains frankie_t's "the opponent cheated," and also why many programmers who barely use AI still feel hollowed out.
There's a pile of earlier experiments too. In 2004, Kruger et al. ran a classic study: the same poem, described to one group as taking eighteen hours to write and to another as taking four, was rated significantly higher in quality and value by the first group. The artifact didn't change—only the human labor behind it did. (Its 2023 replication had mixed results, to be honest.)
The IKEA effect experiments are blunter. Have people fold their own origami, then bid to buy their own creations: they average 23 cents. Observers looking at the same crooked frogs offer only 5 cents. The folders' bids for amateur work approach what observers pay for expert work—and people don't realize how much they're overvaluing their own. The experiment has a cold epilogue: when the work is assembled and then immediately dismantled in front of them, the effect vanishes. Labor must be completed and must persist for love to attach to it.
Put these together and the 2026 situation becomes clear. AI has stripped *effort* out of most software labor: the origami folder still sits at the desk, but the crane was folded by someone else, and another one can be folded in three seconds. You stare at it and can't love it—by the psychology above, that love was never supposed to appear.
The game scholar Jesper Juul, in *The Art of Failure*, argues that games are the only art form that deliberately makes us fail. Failure supplies the stakes; that's what makes winning weighty. Remove the possibility of losing, and winning means nothing.
But don't rush to conclude. A 2020 CHI PLAY study looked specifically at players who cheat, with deflating results: casual players who cheat moderately actually report *better* experiences—more relaxed, more in control. "Cheating ruins the game" holds mainly for achievement-oriented players.
That deflating study may be the key to the whole thread. It accurately predicted the divide in those 175 comments: people who code to *win* were pierced by AI; people who code to *play* were barely touched.
Chess's Thirty-Year Experiment
So what is actually happening to this industry? Chess happens to have run a thirty-year natural experiment, and the results are stranger than anyone predicted.
On May 11, 1997, Deep Blue beat Kasparov 3.5–2.5; in the sixth game he resigned after only nineteen moves. *Newsweek* ran the cover headline "The Last Brain Stand." Kasparov accused IBM of cheating, demanded the machine's decision logs—denied; demanded a rematch—denied. IBM promptly retired Deep Blue. The human world champion lost to the machine, and the machine exited the stage. By this script, chess today should be a museum piece.
The reality: chess.com membership reached roughly 250 million in early 2026; about 1.64 million players worldwide hold FIDE ratings; total viewing time for the 2024 World Championship was 12.9 million hours; and 18-year-old Indian prodigy Gukesh became the youngest world champion in history. A game pronounced dead thirty years ago is now in the most flourishing state it has ever known.
Go offers another set of numbers. When Lee Sedol retired in 2019, he told reporters what is probably the saddest quote in chess history:
> "Even if I become number one, there is an entity that cannot be defeated."
He was 36 that year, losing his farewell match 1–2 to a Korean AI—his one win came from a trick play targeting a known AI weakness. Now look at Korean Go's demographics: total participants fell only about 4% over a decade, yet registered professional and institute players dropped from 3,260 to 1,633—halved—and university Go departments faced closure in 2022. The amateurs held steady; the professional pyramid is shrinking.
The engine didn't kill the people who play. It tore apart *playing the game* and *becoming superior through the game*.
Kasparov himself left the conclusion to this experiment in the *New York Review of Books* in 2010:
> "Weak human + machine + better process was superior to a strong computer alone—and, more remarkably, superior to strong human + machine + inferior process."
This claim has a famous proof. The first freestyle chess tournament in 2005 allowed human-machine teams. The champions were two American amateurs—ratings 1685 and 1398—operating three ordinary computers, defeating the team behind supercomputer Hydra and a string of grandmaster pairs. Top-tier technology lost to better process.
The translation for programmers is effortless: memorizing opening books and calculating variations are the CRUD work. Once the engine devalues those to zero, what remains valuable is understanding, taste, process, and accountability. The agent that blew up during TLS migration was never missing coding ability—it was missing "whose neck is on the line if this goes wrong."
The data supports "rewriting" over "disappearing." The 2025 Stack Overflow Developer Survey: 46% of developers distrust AI output accuracy, exceeding the 33% who trust it; on the biggest pain point question, two-thirds chose "almost right, but not quite." METR ran a randomized controlled trial with 16 senior open-source maintainers using AI on real issues: they were actually 19% *slower*—while estimating they were 20% faster. GitClear analyzed hundreds of millions of lines and found that in 2024, copy-pasted lines exceeded refactored-moved lines for the first time in history. Yet in the same period, GitHub developers grew to 180 million, and TypeScript topped language rankings for the first time thanks to the agent era.
Trust is collapsing, quality is degrading, and the population of practitioners and total innovation are rising. Both things are true at once. The value chain is being rewritten, not eliminated—and in the rewriting, the previous generation's moat gets filled in. For those defending the castle, that is a disaster, no need to sugarcoat it.
Where Did the Joy Go
Lee Sedol and Magnus Carlsen are the control group within the same industry. Lee Sedol's meaning system was anchored to "the summit of humanity"; the engine deleted that coordinate system, and his motivational system collapsed with it. Carlsen said in a 2022 podcast that he personally avoids engine analysis as much as possible—"imperfect knowledge" is worse than no knowledge, but "I love playing chess, and I love winning." He deliberately stays inside imperfection; that's the game he loves.
What was pierced was "winning." It was never "playing."
Psychology has a kindergarten experiment for this too, from 1973. Children who loved drawing were split up; one group was told they'd receive a "good player" certificate for drawing. The certificate recipients subsequently drew noticeably less during free play. The reward had quietly rewritten "I like drawing" into "I draw for rewards." When the reward disappeared—or when everyone got one—the motivation had already changed owners.
AI did the same thing to a generation of programmers, except it withdrew all the external rewards at once: salary premium, scarcity, professional identity, the elite halo of "being able to code." What remains after the withdrawal—do you still write code, or not—is the real answer to the original question.
The answers in the thread were all over the map. Commenter preg_match is writing a new programming language, openly admitting he expects "exactly zero" users besides himself in the AI era: "But I love languages, I love language design. Seeing my own language run and thinking 'I built this'—nothing else replaces that joy." An unemployed commenter turned to photographing spiders, aiming to collect all three species of a certain genus in his state—achieved, and now hunting the next genus. preg_match, on chemotherapy leave, writes code for himself and discovered that what he always hated was the corporate environment; the love had been there all along.
The sharpest and most stable line in the whole thread carries a Stoic flavor:
> "If the meaning of your life can be taken away by someone else, it was always too dependent on external factors."
That line can't silence everyone. Someone in the thread pushed back hard: intrinsic motivation doesn't pay rent—I could lose my current house. Others pointed out that this crisis is layered over a bigger backdrop—financialization, optimizing numbers for shareholders, manufacturing the appearance of value rather than value itself. All valid. Don't use "adjust your mindset" to paper over it. The problem is structural, and so is the pain.
Still, structure aside, each concrete person still faces a choice. It goes roughly like this: suppose the cheat code really exists and is already sitting in your pocket—do you use it, or treat it as the answer key?
The 40-year-old frontend engineer chose to finish first and decide later. The one writing a CLI at 3:30 a.m. chose to keep eating cheese. Two hundred fifty million chess fans, knowing full well the engine is invincible, are playing chess again tonight.
The game isn't over. It's just finally asking you: are you here to win, or to play?