Slop, Alienation, Deskilling, and Team Fallout
58 comments
I have a feeling that this is true and it's a bit sad.
I think there's something deeper than that, too. Almost a feeling of betrayal? I cared in part because I thought everyone else cared, too, like we were working towards a common goal. Asking a question in search of shared understanding only to be passed the modern equivalent of a LMGTFY link hurts in a very particular way. I thought they cared about this, too, but they're only trying to get the bag. I get it, times are difficult right now, but it doesn't make it hurt less.
I wonder if this toxic "Why are you talking to me? Just RTFM or ATFLLM (ask the fucking llm)" attitude can be filtered out during interviewing.
No point crying about it or coping that some bubble will pop and the genie will go back in the bottle. I’m pretty confident that’s not happening, though in the distant future some society will recognize that everything that can be automated should not be automated, that society will look very different and probably won’t happen in my lifetime (it will for one, I predict bring back tailors too).
So here’s my solution, leave the field. If what you enjoyed most was creative problem solving then moving to a field that enables that is the best solution. Yes the next Ruby on Rails app will involve even lesser creativity than before, but is that the situation for the next good aeroplane? Flying car? Small modular nuclear reactor. I suspect just button pushing for that won’t work nearly as well and that’s my plan anyway.
I don't think anyone would care about "hand made software", arguably no one ever did. You need a tool to do X. The enjoyment of the person producing that tool is entirely incidental. You don't care if the corn you're eating was hand picked by a person who loved manual farm labor or by a combine harvester. Just like you wouldn't care if someone enjoys driving a combine vs a self-driving combine nor if someone enjoys directing self-driving harvesters or if they are self-directing.
Outside of that it’s hard to envision handmade anything in software in this everything mass produced cheap consumerist society.
I absolutely do. Perhaps this is a product of my first exposure to computers, but I vividly remember the early Macintosh computers coming on the scene. The care and attention to detail on every level of the machine was special. They were so different than everything before. And it inspired many developers to produce beautiful, weird, awesome software. Does anybody remember the Talking Moose? After Dark? Spaceward Ho! HyperCard? RoboWars? Heck, even MSWord 5.1a was an amazing piece of software whose grammar checker literally taught me grammar.
Now we have “software that does X”, but that X is so bland and enshittified nearly all the joy of computing has been erased. I love writing software. I love writing good and clever software. Perhaps the world no longer cares, but I do.
No, everything that can be automated SHOULD be automated, but the automation should benefit everyone instead of just the 0.1% (actually this percentile keeps getting smaller and smaller, so the percentage of people outside of the "permanent underclass" is probably even less than that now).
The problem about AI (at its current level, barring AI2027 type scenarios) is not about AI, but about the way we've organized society as a whole.
I've brought this up before, if the USSR existed today how would Soviet mathematicians react to AI? Would they be dismayed or overjoyed? You never see mathematicians acknowledge this point, but it's the crux of the issue. In our society employment justifies existence, in a society where existence is inherently justified AI would mean freedom to people instead of causing existential dread.
Yeah, but even once we've achieved a society in which existence is inherently justified, some things are about the destination and some things are about the journey. We need to organize society around producing people and lives, good lives, as the final economic output. A person we "produce" under such a system will probably be highly skilled and want to participate in society's productive processes, because mastery and participation are real human needs for living a good life.
The question is how we distinguish between processes that are important to the people participating in them, and those that are not. Factory work was and is a massive improvement over subsistence farming, but no population in world history has been permanently satisfied spending their lives on the assembly line, so either we can take advantage of highly automated manufacturing to just have machines do the work or we can redirect automation towards re-involving human craftspeople into producing less interchangeable, higher-quality products (the market has been moving towards customizable commodities anyway).
But I dont know if they matter to the employers who can only see LLMs as "free milk", and developers as the "milking machine".
Line Must Go Up.
If treating employees with dignity and giving them intellectually challenging and satisfying tasks make Line Go Up, then that's what employers will do. If making us push "Allow Claude To Do This" hundreds of times over and over makes Line Go Up more, then that's what they'll make us do. If sitting us in a factory and giving only our finger freedom of movement makes Line Go Up, that's what they'll do. If strapping us into pods like in The Matrix makes Line Go Up, that's what they'll do. If feeding us into wood chippers makes Line Go Up, that's what they'll do.
If you cant do that. Destroy the PR and blame the pilot.
And insert some hidden random jokes for me to keep focus»
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.
Also one more thing I started noticing is unnecessarily detailed comments in code, complete with issue numbers. And some of that belong in version control commit (IMHO).
Read the full thread on Hacker News →
Related stories
- The Four Horsemen of Agentic Codingdistantprovince.substack.comLobsters · 22 points · about 8 hours ago
- DEV Community · 22 points · 12 days ago
- Agentic Coding for Builders Who Shipgithub.comHacker News · 1 points · 9 days ago
- Hacker News · 4 points · 10 days ago
- Apex: Agentic coding for mobile and web, fluent in Reactapex.callstack.comHacker News · 1 points · about 24 hours ago
- What Makes Slop, Slop?ampblog.substack.comHacker News · 1 points · 9 days ago