Quantity have quality of it own. Or in case of Code Assistants - speed.
Use Opus fast, Codex-Spark or Cerebras. No more spinner starring. Instant results. One project at time.
Ask HN: How do you maintain flow when vibe coding?
31–38 of 38 posts
Re: Ask HN: How do you maintain flow when vibe coding?
#32AI is yet to solve one of its biggest problems, which is memory. So I trust my memory. I maintain the workflow momentum so I'm always aware of what I did, what I'm doing, and what I'll do. Also, I maintain a lot of markdown files for longer contexts to refer to later. But it's not foolproof. Sometimes I have to rethink the same thing again, and it pushes me in a whole different direction.
Re: Ask HN: How do you maintain flow when vibe coding?
#33[dead]
Re: Ask HN: How do you maintain flow when vibe coding?
#34[dead]
Re: Ask HN: How do you maintain flow when vibe coding?
#35I only use parallel agents when I have simple tasks to get done on all projects. Cleanup, running evals, etc. That whole day becomes parallel agents on easy tasks. Otherwise I do tight feedback loops on single agent (with subagents).
When running multi-agent I recommend keeping an eye on the flow of the work. Is it touching files that make sense? Has it been spiraling too long, is it pulling in packages? Things I can eyeball quickly without fully committing to that context. A full review of that sus diff would make me context switch, but seeing it's editing only files in a related part of the codebase is low effort.
Re: Ask HN: How do you maintain flow when vibe coding?
#36I spent time on this one because context switching was already my baseline before Claude Code because of the nature of my job;
what's worked best: I force myself to ask why I'm launching things in parallel. Is it a real deadline? Back-to-back calls? Or am I just trying to feel more productive? If it's the last one, it's probably not worth it. Very few people actually multitask well. Write the task somewhere ( or have a todo skill that does it for you)
The other piece I picked up from someone writing about this: treat your head like RAM. When you can't avoid a switch, clear it before moving on. Write the note, close the loop, get it out of your head. The lingering open tabs in our heads are the heaviest load, not the switch itself.
Re: Ask HN: How do you maintain flow when vibe coding?
#37I do constantly 3-6 agents simultaneously. It is definatelly exhausting however productivity is through the roof. Make sure to be dynamic and don't follow pre-set patterns. E.g. sometimes you need to switch and just steer (you could quickly), sometimes you need to understand the solution proposed / changes done (it could take hour). Retain the human in the loop and think.
Re: Ask HN: How do you maintain flow when vibe coding?
#38[dead]