As a long time engineer turned manager, I am wanting to build a team environment where people don’t feel like all they are doing is managing slop that is responding to other slop. I feel strongly that these agent based workflows can absolutely be used to great effect to accomplish good engineering. I have a lot of theory and history of previous tech revolutions that tell me the whiplash is part of the adaptation. The pushback I’m seeing is “all my friends who went hard on AI hate their jobs and either have or want to quit” - I don’t think this is universally true though. so I’m looking for either people who have given this a genuinely deep and optimistic try and still have found it to suck terribly, or for folks who found a way. what I don’t want is people who have not given it a real shot and have given up when Claude’s output didn’t succeed after just normal back and forth prompting - what I would call “lazy AI.” my hypothesis is that these are the companies that produce slop - the code works for the problem of the day but not for the systems of tomorrow, and senior engineers are building up resentment and fear while mid level are more productive but don’t see the risks of the slop mountains. has anyone here done this truly well? I’ve seen it work in one other instance, but looking for more nuanced takes. submitted by /u/coordinatedflight
Originally posted by u/coordinatedflight on r/ClaudeCode
You must log in or # to comment.