My first thought is, does this mean that along with the burnout I'm feeling with talking to my own agents I now need to try and consume and understand my teammates conversations with agents? Why is this better than a good pr description that distills completed work and explains why it was required ?
Yes, but compared to seeing 3k lines of code in a PR with no history with vibes in the description, what is better? This definitely "feels" like something worth exploring.
Anyway, I'm probably being over cynical and yes it is worth exploring alternatives to the current system.
However I already feel overwhelmed dealing with agent chats. I can't currently see how this deals with the pr problem:
If I am supposed to delegate to agents why do my conversations need reviewed by my peers. This feels like classic bad management practices of not trusting the staff below you to get on with it, instead turn up in every meeting.
pipes · · focus · HN ↗
lnenad · · focus · HN ↗
pipes · · focus · HN ↗
Anyway, I'm probably being over cynical and yes it is worth exploring alternatives to the current system.
However I already feel overwhelmed dealing with agent chats. I can't currently see how this deals with the pr problem: If I am supposed to delegate to agents why do my conversations need reviewed by my peers. This feels like classic bad management practices of not trusting the staff below you to get on with it, instead turn up in every meeting.