alt Hacker NewsI can't deny that this might be a trend in practice, but at companies with reasonably self-aware practices, it isn't, or doesn't need to be.
There's this weird thing that happens with new tools where people seem to surrender their autonomy to them, e.g. "welp, I just get pings from [Slack|my phone|etc] all the time, nothing I can do than just be interrupted constantly." More recently, it's "this failed because Claude chose..." No, Claude didn't choose, the person who submitted the PR chose to accept it.
It's possible to use tools responsibly and effectively. It's also possible to encourage and mentor employees to do that. The idea that a dev has to be effectively on call because they're pushing AI slop is just wrong on so many levels.
Replies
> More recently, it's "this failed because Claude chose..." No, Claude didn't choose, the person who submitted the PR chose to accept it.
I can relate to this, unfortunately these tools are becoming a very convenient way to offload any kind of responsibility when something goes wrong.
> It's possible to use tools responsibly and effectively. It's also possible to encourage and mentor employees to do that.
It's not in the company's interest to stop employees from overworking. Having people overwork for the same pay under pressure is the desired outcome, actually.