"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.
I miss that flow state. in my past company where i worked as a software engineer, they had this strict no Ai rule, mainly because of data safety. and also because they were building their own Ai agent. because of this forced environment i had to hand code all of the features. i built couple of web components and migrated web apps through major version change. i reached my last memorable flow state during this time. one of the triggers was the dopamine hit you get when you solve something which was not documented anywhere and barely any context available on the internet. Ai has taken away that from me. hand coding is practically impossible nowadays because you always go to the easy door .
I use fast model like Gemini 3.8 Flash and Hydrogen. They allow me to stay involved all the time and experience high level of productivity. They quite often produce code which requires fixes but this keeps me in the loop and focused.
I reach a flow state when I’m coding with AI because, for a while, I forget everything going on in the world. I’ve built over 40 apps under Aldo’s Life (https://apps.aldos.life), and a lot of that flow has gone into each one. So much thought, so much care, so much obsession with perfection, obviously. Apparently, my brain keeps working on the apps while I sleep, because the next morning I wake up and go at it again.
wow i never realized i havent been in a flow state for a while. kinda leaves you as you go from an IC to an executive. I wonder whats the equivalent for a non IC.
The best way is to also be coding on another project yourself while, simultaneously, managing the project your agent is building. When both projects are flowing its pretty nice.
"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.
[0] https://openspec.dev/
I miss that flow state. in my past company where i worked as a software engineer, they had this strict no Ai rule, mainly because of data safety. and also because they were building their own Ai agent. because of this forced environment i had to hand code all of the features. i built couple of web components and migrated web apps through major version change. i reached my last memorable flow state during this time. one of the triggers was the dopamine hit you get when you solve something which was not documented anywhere and barely any context available on the internet. Ai has taken away that from me. hand coding is practically impossible nowadays because you always go to the easy door .
I use fast model like Gemini 3.8 Flash and Hydrogen. They allow me to stay involved all the time and experience high level of productivity. They quite often produce code which requires fixes but this keeps me in the loop and focused.
I reach a flow state when I’m coding with AI because, for a while, I forget everything going on in the world. I’ve built over 40 apps under Aldo’s Life (https://apps.aldos.life), and a lot of that flow has gone into each one. So much thought, so much care, so much obsession with perfection, obviously. Apparently, my brain keeps working on the apps while I sleep, because the next morning I wake up and go at it again.
wow i never realized i havent been in a flow state for a while. kinda leaves you as you go from an IC to an executive. I wonder whats the equivalent for a non IC.
I think some football coaches would describe something like a flow state. That's somewhat analogous to being an executive.
The best way is to also be coding on another project yourself while, simultaneously, managing the project your agent is building. When both projects are flowing its pretty nice.