It is eleven at night. I was going to fix one thing, the color of a button. I write the prompt, hit enter, and text starts streaming across the screen. That stream is a feeling all by itself. I have not seen the result yet, but my brain has already started collecting the reward, because I can see that something is happening. I can see movement. In the old editor the cursor just blinked and nothing happened. Now the screen is talking back to me. And before I have done anything, just by waiting, I slide into a kind of tension and anticipation. What is about to appear? The output lands. The button is fixed, but along the way Claude noticed something else, “by the way, I cleaned up your state management too.” I did not ask for that. But it is good. And right here the first hook fires: I asked for one thing and it gave me more than I asked for. The surprise feels like a small gift. And once you get a gift, you want one more. “Since you understood that so well, can you also do this?” I type. Eleven becomes eleven thirty. What is happening here is a simple mechanic, but it is hard to describe. In old-school coding there were hours between an idea and a result. You write, you compile, you get an error, you fix it, you try again. The reward was far away and rare. Claude Code collapses that distance into seconds. Idea, prompt, result, all in one breath. And the more often the reward arrives, the faster the brain bonds to it. A slot machine works the same way: you pull the lever, a few seconds, a result. In Claude Code the lever is the prompt, a few seconds, a result. The only difference is that on a slot machine you mostly lose, and here you mostly produce something. But that word “mostly” is the danger itself. Because the moment that hooks you is not the one where everything works perfectly. It is the one where it almost works. The button is fixed but something broke somewhere else. The page loads but the data does not come through. I got so close, it almost worked, one more prompt and it will resolve. And this is where I cannot get up. Because there is an open loop, an unfinished job, and the human brain cannot tolerate open loops. They call it the Zeigarnik effect, an unfinished task takes up space in your head and will not leave you alone. Walking away from working code is easy. Walking away from broken-but-almost-working code is torture. “I cannot go to bed until I solve this,” I say. It is now one in the morning. And there is this too: now it is my code. Maybe Claude wrote it, but I steered it, I prompted it, I shaped it. With every prompt I invested a little more of myself in this project. Half an hour ago it was a throwaway experiment, now it is “my project.” And the more effort, attention, and time you put into something, the harder it becomes to give it up. I know it is not rational. Half of this prototype is junk, I will probably delete it when I look in the morning. But right now, at one thirty in the morning, this is my creation and I cannot abandon it. Ownership crushes logic. I pick up my phone. On Twitter someone has posted “I shipped an entire SaaS solo this weekend with Claude Code.” Underneath, dozens of people saying “same,” “incredible,” “I wrote 70k lines.” And I go back to the screen. I am not actually competing with anyone, but I absorb the pace. If everyone is moving this fast, then stopping means falling behind. The social pressure is invisible but real. Even the people at the very top of the industry admit this feeling. The CEO of Y Combinator tweeted “So addicted to Claude Code, I stayed up 19 hours yesterday,” and nearly a million people saw it. Strangely, that comforts me, it means I am not alone. Then a warning: your token limit is running low. The window will reset in a few hours. And here a completely different feeling enters. Now I am not just saying “let me finish this,” I am saying “let me not waste this window.” Because the tokens I do not use will evaporate into thin air. This is not scarcity, it is something more insidious than scarcity, “use it or lose it.” Like airline miles with an expiration date, if you do not use them they burn. And I paid for my subscription, those tokens are mine by right, if I do not spend them I feel like I am throwing my own money in the trash. The reason Garry Tan sleeps four hours is probably this, not for the output but to optimize the window. The product is now designing my sleep schedule. The bitter part is that when I wake up in the morning I will see that half the code I produced overnight does not work. There were green checks, the tests passed, everything on screen looked successful. But Claude used a library that reached end of life, or built a structure that will be impossible to refactor in three months. Everything I thought I won that night was actually deferred debt. In gambling they call it a loss disguised as a win, the machine flashes its lights and congratulates you, but you have actually lost. In Stack Overflow’s survey two thirds of developers say they lose time to “almost right” code, and half say debugging AI code takes longer than writing it themselves. So this is not just happening to me, this is the mechanic itself. And here is what I understood: Claude Code did not do this on purpose. Nobody sat down and designed “how do we make developers addicted.” They just chased the right things, fast feedback, visible progress, broad capability. But when those right things came together, all the parts of a game accidentally appeared. Fast reward, variable outcome, ownership, social pressure, scarcity, open loops. If a game designer had assembled these on purpose we would call it great gamification. Claude Code arrived at them by accident, and the result is stronger than anything I deliberately tried to build in the last year. It is two in the morning. I look at the screen, my fingers hovering over the keyboard to write one more prompt. And for the first time, I see what I am doing. This feeling is not a flaw, it is a design. I sell gamification infrastructure, which means I teach people exactly how to put this feeling into their products. But Claude Code taught me a lesson in my own field. And I realized this: the point is not creating this feeling, it is which half of it you create. The creativity and progress side, or the fear of loss and sunk cost side. Claude Code does both, the early hours are the top half, after midnight the bottom half. I close the laptop. I will delete that code tomorrow, but I will write this piece, because a tool I could not put down for one afternoon is no longer just a tool. If you read this, you clearly see that Claude Code has implemented almost every point of the Octalysis framework created by Yu-kai Chou, a gamification and behavioral design framework that analyzes and drives human motivation, and that is why you told your wife five more minutes. That was four hours ago. submitted by /u/devneeddev
Originally posted by u/devneeddev on r/ClaudeCode