Earlier quoted context omitted.
It's a matter of definition, a flow state is hitting peak performance without attending to the details of your actions, fluidly and without delays, at a task that in any normal situation would be considered complex and difficult. If you know the feeling from performance or from trance-like coding sessions, there's no mapping of that to the use of agents as described in this article. It's not that I don't achieve it,…
I know the feeling from hours long guitar jam sessions. I have definitely gotten there with some recent projects using Claude Code.
Getting into Flow State with Agentic Coding
11–20 of 30 posts
Re: Getting into Flow State with Agentic Coding
#12Earlier quoted context omitted.
I know the feeling from hours long guitar jam sessions. I have definitely gotten there with some recent projects using Claude Code.
Would you mind sharing an example project?
https://github.com/williamcotton/webpipe
And a work in progress article about it:
Re: Getting into Flow State with Agentic Coding
#13Re: Getting into Flow State with Agentic Coding
#14I disagree that you can reach what I would call a flow state with such a degree of non-participation but I entirely agree that planning first makes execution better, for both humans and agents.
I can't reach flow with agent coding because as soon as I set it running I flip over to something else and come back later. I think this is a problem with the current agents, though. If it responded immediately with its ideas and code then I wouldn't flip away and could stay present.
> flip over to something else
A flow state is possible with 100% focus at any level of abstraction.
If you just "flip over" to HN while the agent thinks, then you're not 100% focused.
But if you're managing three agents at the same time on the same codebase, and while Agent 2 is thinking you "flip over" to Agent 3, you're still fully participating, just at a higher level of abstraction.
Re: Getting into Flow State with Agentic Coding
#15I disagree that you can reach what I would call a flow state with such a degree of non-participation but I entirely agree that planning first makes execution better, for both humans and agents.
I can't reach flow with agent coding because as soon as I set it running I flip over to something else and come back later. I think this is a problem with the current agents, though. If it responded immediately with its ideas and code then I wouldn't flip away and could stay present.
Re: Getting into Flow State with Agentic Coding
#16Re: Getting into Flow State with Agentic Coding
#17Doe-eyed self-reporting is not credible.
Re: Getting into Flow State with Agentic Coding
#18Earlier quoted context omitted.
Would you mind sharing an example project?
I was harassed the last time I shared something, but oh well, here is a work in progress DSL: https://github.com/williamcotton/webpipe And a work in progress article about it: https://williamcotton.com/articles/introducing-web-pipe
Re: Getting into Flow State with Agentic Coding
#19Earlier quoted context omitted.
I was harassed the last time I shared something, but oh well, here is a work in progress DSL: https://github.com/williamcotton/webpipe And a work in progress article about it: https://williamcotton.com/articles/introducing-web-pipe
I'm just curious, I don't intend to harass anyone. Are you considering including the prompts in the published article?