alt Hacker NewsThat's a choice (unless your management thinks otherwise). I don't need my agents running non stop. I tell them to start running once my walk is completed and I have a clear vision of what I want them to do.
That's a choice (unless your management thinks otherwise). I don't need my agents running non stop. I tell them to start running once my walk is completed and I have a clear vision of what I want them to do.
It seems to me this is the most reasonable approach. Using LLMs to remove the cognitive load from implementation details, scaffolding, and taking it from there to production grade code. In short, like an IDE on steroids.
I'm curious and hear a lot about agentic programming, yet hear little about the cognitive load from it. Having more code generated doesn't make you more productive, in fact, I would argue the contrary is the case. There's more code to understand, more code to discard, an extra decision (which result do I pick? How do I split the workload through my agents), which is not at all how we operate (I. E context switching, limited by our cognitive energy, working task by task).
I really don't buy the whole agentic thing. The only reasonable use case I can see for it, is to scaffold multiple projects at the same time.