LLM slopcannons are putting pressure on top of already broken software dev team cultures. The problem isn't the slop generator, so much as your process was only handling low volumes of human-generated slop until now.

@nateberkopec I agree that human devs aren't infallible and team processes aren't always good.

I'd stop short of blaming the humans for not adapting to the slop factory, though. The team's processes serve the team to an extent. If the slop factory doesn't, but the humans have to adapt to it, then it is indeed the problem.

Humans use machines to make things easier for ourselves. If we have to serve the machine, that's exactly the wrong direction.

@jamie software doesn't exist to serve the developers either. it exists to serve it's users.
@nateberkopec The two ideas aren't mutually exclusive. You can have software that serves it users and a development process that serves the developers.

@nateberkopec Another problem is that software lately *hasn't* been serving the user. Software quality is in the gutter across the board. And customer support teams have been gutted for the same reasons.

Blaming LLM slop factories seems pretty fair here. 😄

@jamie this is where our values diverge. I do not believe the development process exists to serve the developers at all, full stop.
@nateberkopec That surprises me. Why not?

@jamie I work on software for other people's benefit, not my own. OFC I'm not saying it's ok for my working conditions to suck or be terrible, but I'm doing this for them, not me. I'm in it for the end product.

OSS is the inversion of this: my opensource projects are the byproduct of development done purely for my own enjoyment.