Live data from Hacker News

How much can you delegate to agents?

newsletter.posthog.com

1–10 of 24 posts

Re: How much can you delegate to agents?

#3
Interesting. When it comes to auditing, I think there is also another layer to be verified - the intent. We have tooling for static analysis and automated tests, but drift in intent or vision is hard to detect.

After leaving agents unsupervised for longer periods of time, the biggest questions tend to be "how did it arrive at this conclusion?" and "did we drift from the initial vision?". Typically these questions are hard to answer as you only review the final state of the workflow.

I recently built an issue tracker that does offer time-traveling as a core feature. Somewhat unexpectedly this turned out to provide a much sought for overview allowing for a better workflow audit, as detailed here: https://dev.to/ljtn/vision-drift-addressing-the-next-problem...

Would be interested to hear your thoughts. I guess vision drift would classify as something that is hard to reverse, because you often don't realize it has happened until much later.

Re: How much can you delegate to agents?

#6
I work on my MacBook in direct terminal sessions or in a container with no safeguards.

I save the container for well-planned units of work that can easily be repeated and validated on a branch.

I use direct sessions when I expect and the plan dictates that Claude might go off target and I need to hold the steering wheel.

Fable has increased my use of the container option.

Re: How much can you delegate to agents?

#10

This is a very long form way of saying “understand the work you are dispatching, and if you don’t, ask questions until you do”

> “understand the work you are dispatching, and if you don’t, ask questions until you do”

My rant about this, not directed to the commenter but in general:

I wish people would have been so interested on discussing and planning with teammates like they seem with AI tools.

Because this is nothing new. Communication, knowing what you are doing, planning... was already a mandatory step for any engineering task.

And if people that use planning with AI then ignore their teammates, other teams, etc. then it is time to reconsidering their way of working.

Post reply on HN