Call me crazy, but I absolutely LOVE using AI, especially coding agents.
This has been the most euphoric period of my career so far, and it’s not even close. Locking myself in the terminal with N windows open, agents running in each, and orchestrating the whole thing iteratively is absolutely insane!
The dopaminergic treadmill is such that I have to force myself to stop. Usually this happens when my brain starts turning to mush because I’ve been context switching nonstop for 2–3 hours. Pre-AI, I experienced this too, but it happens a lot more often these days.
Needless to say, I’m having a lot of fun. This picture represents quite well how I feel when I work with multiple agents at once:
More than waiting on prompts
I was on r/ExperiencedDevs the other day, and it’s honestly disheartening how many people seem to hate everything related to AI. I hear some of this from coworkers too, but under the anonymous veil that Reddit provides, people are much more blunt about it.
One comment pattern keeps coming up: “I used to code and solve problems. Now I just write prompts and wait”, or some variation of this.
Huh. My first reaction was that if you’re spending your time waiting on prompts to finish, then you’re probably missing a big part of what makes these tools useful.
Here’s what working with them looks like for me at the moment:
I run agents in separate tmux windows and move between them to review results, give direction, and decide what needs my attention.
I use a terminal tool I built to keep track of agent sessions. I can adapt it however I want as I refine my workflows.
Alongside that, I explore ideas, ask questions, and work through concepts I don't fully understand yet.
While an agent works through one task, I can be thinking about another part of the project. That’s where a lot of the fun comes from: several things are moving, and I can keep engaging with the problem from different angles.
Of course, there has to be something useful to move forward. Opening another terminal window isn’t an accomplishment by itself.
But yeah, “prompt, wait, repeat” doesn’t describe most of my experience. And initially, I assumed that explained why some people weren’t enjoying coding agents.
I’m still solving things
I also have trouble relating to the idea that the problem-solving disappears, which is also a common sentiment in software engineering discussion spaces.
I don’t know, man. I still feel like I’m solving things quite a bit!
I still have to understand the problem, choose an approach, and decide whether the implementation actually makes sense. Code can look perfectly reasonable and still solve the wrong problem or introduce an abstraction that doesn’t belong. These agents still need guidance.
Then there are the questions specific to working with agents:
| Topic | What I have to figure out |
|---|---|
| Delegation | What’s a useful unit of work to hand over? |
| Context | What does the agent actually need to know? |
| Instructions | How do I communicate what I want precisely and accurately? |
| Intervention | When should I step in, and when should I let it continue? |
| Progress | Am I moving the project forward, or just keeping agents busy? |
The problems are different now, but they’re still problems. Some are non-trivial, with interesting research underway on how to solve them.
That doesn’t mean they’re an equally satisfying replacement for everyone. If implementing the solution yourself was your favorite part, I can understand why having more orchestration problems to solve wouldn’t make up for it.
But another comment made me reconsider something more fundamental about my reaction.
Maybe I’m just lucky?
This particular Reddit comment caught my attention:
I used to wear headphones all the time because I would lock in with music and get a bunch of shit done
With AI none of that happens anymore, I can’t get into deep focus because I’m context switching between 2-3 things at once. It’s just a different job now
I think I might be lucky in how my concentration mechanism functions.
I’ve generally found it easy to switch between tasks and get back into whatever I was doing, for as long as I can remember. If someone interrupts a session to ask for help, I can usually drop what I’m doing, help them, then come back and pick up where I left off.
The switching still tires me out after a few hours, but it rarely breaks my momentum or puts me in any bad mood.
As I’ve progressed in my career, though, I’ve met many excellent engineers who need an uninterrupted stretch with one problem to really get into it.
And that’s where my initial reaction starts falling apart.
Someone says they can’t concentrate because they’re switching between tasks, and my instinct is to suggest that they make better use of parallelization. I’m recommending more of the thing they’re struggling with.
Maybe there’s a loose DFS vs. BFS analogy here: following one thread deeply, or advancing several in turns.
What I’m taking away
I don’t know how much of the disagreement this explains. But it makes me question how quickly I went from “this works incredibly well for me” to “other people must be missing something that I’m seeing.”
Maybe the useful question is how to fit agents around your concentration mechanism. For me, it’s reasonable to have several things moving at once. For someone else, it might mean one agent, one problem, and fewer interruptions.
The best workflow might be the one that helps you stay focused and keep your momentum.
