4 ms·

The Dopamine Trap of Vibe Coding

4 points by romanhoffmann 7mo ago

romanhoffmann 7mo ago
I've been experimenting a lot with AI-assisted development lately and noticed a strange pattern. The feedback loop becomes extremely fast: prompt → result → tweak → repeat. That speed creates a kind of variable reward system where near-misses keep you iterating longer than planned. I also started noticing things like thinking about prompts late at night or waking up early wanting to try "just one more idea". This post is an attempt to describe some of the psychological effects behind that experience. Curious if other developers noticed similar patterns when using LLM coding tools.
- operatingthetan 7mo ago
  Are you front-loading your planning before you let the agent start coding? That might help.
  - romanhoffmann 7mo ago
    Good question. In my own projects I actually front-load a lot of the planning. The pipeline behind codn.dev is a good example of that — the planning phase was longer than the actual prompting. I started with a very simple Astro project and then gradually designed the publishing workflow around it: content schema, frontmatter structure, SEO generation, deployment pipeline, etc. Only after that foundation existed did I start using LLMs to help with parts of the implementation. The pattern I describe in the article is less about "one prompt shipping", and more about what happens once the feedback loop becomes very fast. Even with a plan in place, the prompt → result → tweak cycle can become surprisingly sticky.
deleted 7mo ago
[deleted]
selfradiance 7mo ago
[flagged]
- ahmed-fathi 7mo ago
  The write-down-where-you-left-off trick is underrated. I think it works because it gives the brain a kind of "closed" signal the open loop that Zeigarnik describes gets a placeholder, so the mind stops simulating. A physical notebook works better than a digital note for this, at least for me. Something about closing an actual object.
ascent817 7mo ago
This really hit home for me. Before vibe coding, I'd only go on coding binges maybe once a month (coding for 8 hours straight). Now with AI, the velocity is addictive. My coding binges have become much more frequent but sadly less satisfying.
toniantunovi 7mo ago
The dopamine loop framing is spot-on. The "it compiles and the tests pass" feedback cycle is genuinely intoxicating, and it's very different from the slower, more uncertain feeling of writing careful code yourself. What's interesting is that the same AI tools that create the loop can partially break it if you add a mandatory quality gate between "agent generates code" and "you merge it." The friction of seeing a linting/security report before you hit merge forces a moment of actual review that the vibe coding flow otherwise eliminates.

4 points by romanhoffmann 7mo ago

I've been experimenting a lot with AI-assisted development lately and noticed a strange pattern. The feedback loop becomes extremely fast: prompt → result → tweak → repeat. That speed creates a kind of variable reward system where near-misses keep you iterating longer than planned. I also started noticing things like thinking about prompts late at night or waking up early wanting to try "just one more idea". This post is an attempt to describe some of the psychological effects behind that experience. Curious if other developers noticed similar patterns when using LLM coding tools.

operatingthetan 7mo ago
Are you front-loading your planning before you let the agent start coding? That might help.
- romanhoffmann 7mo ago
  Good question. In my own projects I actually front-load a lot of the planning. The pipeline behind codn.dev is a good example of that — the planning phase was longer than the actual prompting. I started with a very simple Astro project and then gradually designed the publishing workflow around it: content schema, frontmatter structure, SEO generation, deployment pipeline, etc. Only after that foundation existed did I start using LLMs to help with parts of the implementation. The pattern I describe in the article is less about "one prompt shipping", and more about what happens once the feedback loop becomes very fast. Even with a plan in place, the prompt → result → tweak cycle can become surprisingly sticky.

deleted 7mo ago

[deleted]

selfradiance 7mo ago

[flagged]

ahmed-fathi 7mo ago
The write-down-where-you-left-off trick is underrated. I think it works because it gives the brain a kind of "closed" signal the open loop that Zeigarnik describes gets a placeholder, so the mind stops simulating. A physical notebook works better than a digital note for this, at least for me. Something about closing an actual object.

ascent817 7mo ago

This really hit home for me. Before vibe coding, I'd only go on coding binges maybe once a month (coding for 8 hours straight). Now with AI, the velocity is addictive. My coding binges have become much more frequent but sadly less satisfying.

toniantunovi 7mo ago

The dopamine loop framing is spot-on. The "it compiles and the tests pass" feedback cycle is genuinely intoxicating, and it's very different from the slower, more uncertain feeling of writing careful code yourself. What's interesting is that the same AI tools that create the loop can partially break it if you add a mandatory quality gate between "agent generates code" and "you merge it." The friction of seeing a linting/security report before you hit merge forces a moment of actual review that the vibe coding flow otherwise eliminates.