| ▲ | Zambyte 7 hours ago | |
"vibe coding" is, by definition, mentally unengaging. You offload technical cognitive tasks to your agent, and operate more in an emotional mental state, rather than one that demands logic and reasoning effort. I believe flow state is much easier to achieve when you're actually chaining together tasks that demand logic and reasoning effort. You can do this by simply not offloading those tasks to your agent. That is not to say you can't get there while using AI to assist your coding, but it is to say you probably can't get there while vibe coding. I personally drive most of my coding tasks using spec driven development. I use OpenSpec[0] for this, which I do recommend, but the specific implementation probably doesn't matter all that much. The key here is that I will iterate on spec documents, sometimes for hours, before telling my agent to implement the spec. I read every single line and make sure that I am actually happy with it and agree with the proposed changes. This doesn't use tokens as fast as possible as many people like to - I'm often sitting with all agents idle as I sit and comprehend the proposals for myself. That's a trade-off that I find worthwhile for my own comprehension and engagement in the project though. | ||