And I am just a support person, so not directly affected. My core tasks are to support customers and to provide input to developers about the common points of struggling.
While one agent is busy, you can start another agent on a different task. (Or maybe even the same task with a variation in the prompt. To hedge against the unlikeliness of the first agent always one-shotting acceptable code.)
Even if you aren't verifying the resulting code, prompting six different agents and confirming their results should keep you busy. (I guess you could even do more if you wanted...)
> Now I see him spending most of his time doing what product managers traditionally do: talking to users, understanding their problems deeply, figuring out what's actually worth building. Coding has become maybe 20% of his job, and even that 20% is mostly about understanding requirements and translating them into clear specifications. The actual implementation work that used to consume 80% of his time is now handled by machines.
From a recent submission: https://donado.co/en/articles/2025-09-16-vibe-coding-cleanup...
And I am just a support person, so not directly affected. My core tasks are to support customers and to provide input to developers about the common points of struggling.
You can fill the gaps with more "Vibe Coding."
While one agent is busy, you can start another agent on a different task. (Or maybe even the same task with a variation in the prompt. To hedge against the unlikeliness of the first agent always one-shotting acceptable code.)
Even if you aren't verifying the resulting code, prompting six different agents and confirming their results should keep you busy. (I guess you could even do more if you wanted...)
I have seen various descriptions of this type of workflow. Most recently: https://hw.leftium.com/#/item/45180353
> Now I see him spending most of his time doing what product managers traditionally do: talking to users, understanding their problems deeply, figuring out what's actually worth building. Coding has become maybe 20% of his job, and even that 20% is mostly about understanding requirements and translating them into clear specifications. The actual implementation work that used to consume 80% of his time is now handled by machines.
Also here is a short video of this type of workflow in action: https://www.youtube.com/shorts/tP1fuFpJt7g
I'm solving problems that LLMs assist with, but are unreliable. Using vibe coding or Agents sounds like a disaster.
There isn't any real gap time. It tends to generate things quickly, then you have to code review it all.
When taking a break from tending my agents, I like to eat lunch, some exercise or check on other work and emails.
I smoke cigars and watch sports
maybe it can write code, but it still sucks at technical editing