Agentic Coding's Four Horsemen: Slop, Alienation, Deskilling, and Isolation

The Four Horsemen of Agentic Coding

Agentic Coding's Four Horsemen: Slop, Alienation, Deskilling, and Isolation

Agentic coding is undeniably useful, but it's also wreaking havoc on software engineering. LLM-generated code has a distinctive 'slop' smell that makes codebases repulsive to humans. Engineers become alienated from their craft, caring less about the code they produce. AI erodes existing skills and impedes learning, with no meaningful skill progression. And agents weaken team social bonds by reducing interpersonal communication and increasing self-reliance. The author sees no solution in sight.

However beneficial AI is, we pay dearly for it with our curiosity, craftsmanship, and social connection.
  1. BatchJob

    Its inspiring to see folks putting effort into verbalizing the conflicts and unexpected side effects of working with LLMs. Our feelings really do matter at the end of the day.

    But I dont know if they matter to the employers who can only see LLMs as "free milk", and developers as the "milking machine".

  2. tschellenbach

    It is very possible to use these tools in the wrong way. Companies that understand how to use AI will do better, those that have these 4 problems won't.

    - AI should accelerate your understanding of the codebase and technical concepts.

    - Skills should ensure a higher quality of code than you could create without AI

    - Engineers should stay responsible for the code they product.

    - The available time freed up should be used for communication, product and marketing research. The definition of an engineer who just writes code is something that's going away.

    Unless something is so simple that the AI can run it autonomously. There are actually many projects like that these days. And in those cases not looking at the code like DHH does is also a viable strategy.

  3. headcanon

    I feel like I'm living in an alternate universe - my company has fully adopted agentic coding, we're working with:

    - large codebases

    - business critical software for clients that don't tolerate downtime

    - agentic and classical features

    We still collaborate well, we still care about quality, we still have good knowledge of the codebase, but I haven't written a single line of code myself in over a year.

    We have not had a single incident that I'm aware of where we shipped a slop and it created downtime.

    We're building a "software factory" that is currently handling low-level chore tickets and merging about 1/3rd of our PRs. A year from now I imagine it will be doing significantly more, and I don't think anyone is going to get fired because of it (if anything we'll keep hiring more).

    I don't see this as an either/or thing. If there is some hidden ocean of slop that we're bound to fall into I don't see it anywhere. Where is the disparity?

  4. paularmstrong

    My work Slack channels are ghost-towns. People are logged in, but they're never saying anything. I often find myself wondering if anyone is even working. PRs have their names on them, even the review comments are posted from _their_ accounts, but it is obvious that Claude wrote everything from the code, the unnecessarily verbose change summary, to their comments. Even their replies to my change requests start with "You're right — …".

    I miss the days when the engineering Slack channels had long threads of new and interesting ways to do things, discussions of something we could do next to make work easier or fix long-standing issues. We used to build up our own knowledge of who was good at specific things, what they'd be interested in working on. Now everyone just has their slop-machine spit out every piece of a change for the entire stack without paying any attention to the details.

  5. advael

    I agree with everything in this article (though I am still optimistic that LLMs will help otherwise unskilled people write personal software), but unless labor starts meaningfully organizing and pushing back against the corporate power that causes these outcomes, things will only get worse

    Like we can say "this sucks" twenty thousand times, but what's the plan? Maybe some of the senior people who can be productive because of our knowledge who may cease to exist as a class resulting in a century of slop should get together and talk praxis. Otherwise all these articles are just training data

More from this day

2026-10-02