Once again, the problem is that people ignore all of the invisible costs of vibe coding:

- prompting (specifying what to do *takes time*)
- learned helplessness
- constantly interrupting their own flow state
- babysitting rules files
- reviewing the LLM's output
- fixing bugs introduced by the LLM

Vibe coding doesn't make programming labor disappear

Vibe coding transmutes programming labor into code review labor and engineering management labor, both of which are (in my experience) more labor-intensive than programming