I just registered my kid for fall school athletics, and now feel like Heracles returning from the underworld with Cerberus on his back.
-
For things like child athletic registration, you have to do it once per season and once you've sorted out what time and place and with whom your kid is going to play, you're not going to switch leagues or academies or whatever just because the registration software was crap.
The really irksome thing is that crap forms are of course nothing new, but for most of the decade of the teens improvements in software made it easier for a basic programmer to write good, functional forms with good validation and sound error messages.
Now we're going hard into reverse because no one wants to even pay a basic software dev anymore and bosses have decided that no one cares.
@MichaelTBacon @mk30 @inthehands to add to this: the parent doesn't directly pay for the registration portal, the league or city or school of whoever does. Some school administrator is the person the software needs to be sold to, and they'll only ever see a slide deck, not the actual software. Once they've picked between slide decks, inertia makes it extremely expensive to switch, no matter how many reports they get from parents (if any; they probably never hear about the vast majority of the problems). So there's really very little incentive to make the software work well, especially when all the competitors' software is also horribly broken.
Even when there are real feedback forces (enough complaints get the district to switch software, resulting in a significant loss to the company) they're out beyond the planning/caring horizon of most CEOs. Are you really going to invest in sprucing up the "already working" software just because in 2 years you might lose a contract? Or would you rather tell that engineer to work on something shiny and new?
-
OK, I guess I wasn't done after all.
Much of the opining about developer backlash to LLMs falls into two loose theoretical categories:
(1) Labor problem: developers now experience employment threat, loss of job security, layoffs, new levels of worry about the future
(2) Identity problem: developers used to feel special because generating code was placed on a cultural pedestal (sign of a special third brain lobe or whatever), that perceived specialness was a pillar of our personal identity, and now our egos are bruised because machines can do it and we don’t feel special anymore
While there’s doubtless truth to both of those in some / many cases, I posit a third theory:
(3) Purpose problem: contrary to popular belief, developers actually care quite a lot about the people who use our software and we derive a sense of purpose and meaning from doing what we believe to be good work; the current environment undermines that, not just LLMs but LLMs as part of a broader vortex of enshittification, and our world is effectively saying “everything you cared about doesn't matter, you can't hope to fight to make it matter, and you are stupid for caring”
I think there's evidence for that last theory in the kinds of despair you hear from developers: not just anxiety about paying the bills, not just angry feather-puffing, but a kind of existential despair that comes from the unraveling of one’s internal sense of purpose and meaning.
4/3
@inthehands There is a fine line between identity and purpose. You can retain identity but losing purpose for that identity is deadly because once the purpose is gone, why hang on to the identity?
-
OK, I guess I wasn't done after all.
Much of the opining about developer backlash to LLMs falls into two loose theoretical categories:
(1) Labor problem: developers now experience employment threat, loss of job security, layoffs, new levels of worry about the future
(2) Identity problem: developers used to feel special because generating code was placed on a cultural pedestal (sign of a special third brain lobe or whatever), that perceived specialness was a pillar of our personal identity, and now our egos are bruised because machines can do it and we don’t feel special anymore
While there’s doubtless truth to both of those in some / many cases, I posit a third theory:
(3) Purpose problem: contrary to popular belief, developers actually care quite a lot about the people who use our software and we derive a sense of purpose and meaning from doing what we believe to be good work; the current environment undermines that, not just LLMs but LLMs as part of a broader vortex of enshittification, and our world is effectively saying “everything you cared about doesn't matter, you can't hope to fight to make it matter, and you are stupid for caring”
I think there's evidence for that last theory in the kinds of despair you hear from developers: not just anxiety about paying the bills, not just angry feather-puffing, but a kind of existential despair that comes from the unraveling of one’s internal sense of purpose and meaning.
4/3
Put more concisely:
I’d bet money that developer reaction to LLM-driven development would be •very• different if its practical effect were to force management to slow down development and sink more money into quality.
5/3
-
@MichaelTBacon @mk30 @inthehands to add to this: the parent doesn't directly pay for the registration portal, the league or city or school of whoever does. Some school administrator is the person the software needs to be sold to, and they'll only ever see a slide deck, not the actual software. Once they've picked between slide decks, inertia makes it extremely expensive to switch, no matter how many reports they get from parents (if any; they probably never hear about the vast majority of the problems). So there's really very little incentive to make the software work well, especially when all the competitors' software is also horribly broken.
Even when there are real feedback forces (enough complaints get the district to switch software, resulting in a significant loss to the company) they're out beyond the planning/caring horizon of most CEOs. Are you really going to invest in sprucing up the "already working" software just because in 2 years you might lose a contract? Or would you rather tell that engineer to work on something shiny and new?
This is exactly right, and there's the added bit that in 2026 the CEO of Arbiter Sports isn't thinking, "we've got to round out our customer focus and improve page responsiveness, and demonstrate value over competitors." He's (and 95% change this company is run by a tech bro) thinking, "we have to be on the forefront of AI innovation and vibecoding!"
Do I think they will all deeply regret that focus in 2-3 years? Absolutely. Do I think I could convince them of that right now? No chance.
-
Put more concisely:
I’d bet money that developer reaction to LLM-driven development would be •very• different if its practical effect were to force management to slow down development and sink more money into quality.
5/3
@inthehands Here is a good faith argument in favor of AI assisted coding. We, the blind community, have been asking for years to make accessibility a priority in software development. For decades we've heard "it’s not on the roadmap". So we decided, with the help of AI, to take matters into our own hands.
-
OK, I guess I wasn't done after all.
Much of the opining about developer backlash to LLMs falls into two loose theoretical categories:
(1) Labor problem: developers now experience employment threat, loss of job security, layoffs, new levels of worry about the future
(2) Identity problem: developers used to feel special because generating code was placed on a cultural pedestal (sign of a special third brain lobe or whatever), that perceived specialness was a pillar of our personal identity, and now our egos are bruised because machines can do it and we don’t feel special anymore
While there’s doubtless truth to both of those in some / many cases, I posit a third theory:
(3) Purpose problem: contrary to popular belief, developers actually care quite a lot about the people who use our software and we derive a sense of purpose and meaning from doing what we believe to be good work; the current environment undermines that, not just LLMs but LLMs as part of a broader vortex of enshittification, and our world is effectively saying “everything you cared about doesn't matter, you can't hope to fight to make it matter, and you are stupid for caring”
I think there's evidence for that last theory in the kinds of despair you hear from developers: not just anxiety about paying the bills, not just angry feather-puffing, but a kind of existential despair that comes from the unraveling of one’s internal sense of purpose and meaning.
4/3
Number 3 is me.
I've been writing my software for 23+ years. As an employee, a contractor, and then as a partner with a larger percentage of ownership each year until I owned it all.It's my baby, it feeds the employees in my tiny company, and runs the businesses of my ~85 clients.
I'm going out of my way not to enshitify our product, and to continue to provide quality and value, and I'm not going to let LLMs near our code (for both the ethical and technical reasons).
-
“Doesn't the bottom line get affected by broken software?”
Ah, the trillion-dollar question.
Under consumer capitalism, in a competitive market? Yes.
Under investor capitalism, in a world of monopoly and capture and extraction? No, no it does not.
@inthehands @mk30 I only started to understand the damage of monopolies and anti-competitive behaviour after reading Matt Stoller.
His dissection of Amazon Prime was eye opening.
https://www.thebignewsletter.com/p/amazon-primes-free-shipping-promiseBut then I read his post about anti-competitive cheerleading and my mind was blown. Cheerleading... If something like cheerleading can be monopolized, is there anything safe?
https://www.thebignewsletter.com/p/antitrust-and-the-fall-of-a-cheerleading -
OK, I guess I wasn't done after all.
Much of the opining about developer backlash to LLMs falls into two loose theoretical categories:
(1) Labor problem: developers now experience employment threat, loss of job security, layoffs, new levels of worry about the future
(2) Identity problem: developers used to feel special because generating code was placed on a cultural pedestal (sign of a special third brain lobe or whatever), that perceived specialness was a pillar of our personal identity, and now our egos are bruised because machines can do it and we don’t feel special anymore
While there’s doubtless truth to both of those in some / many cases, I posit a third theory:
(3) Purpose problem: contrary to popular belief, developers actually care quite a lot about the people who use our software and we derive a sense of purpose and meaning from doing what we believe to be good work; the current environment undermines that, not just LLMs but LLMs as part of a broader vortex of enshittification, and our world is effectively saying “everything you cared about doesn't matter, you can't hope to fight to make it matter, and you are stupid for caring”
I think there's evidence for that last theory in the kinds of despair you hear from developers: not just anxiety about paying the bills, not just angry feather-puffing, but a kind of existential despair that comes from the unraveling of one’s internal sense of purpose and meaning.
4/3
@inthehands In a related vein I read this the other day and thought it was good
https://ryancheley.com/2026/08/17/what-if-maintainer-burnout-isn-t-burnout/
-
Number 3 is me.
I've been writing my software for 23+ years. As an employee, a contractor, and then as a partner with a larger percentage of ownership each year until I owned it all.It's my baby, it feeds the employees in my tiny company, and runs the businesses of my ~85 clients.
I'm going out of my way not to enshitify our product, and to continue to provide quality and value, and I'm not going to let LLMs near our code (for both the ethical and technical reasons).
Good luck and godspeed. You are not alone in this!
-
OK, I guess I wasn't done after all.
Much of the opining about developer backlash to LLMs falls into two loose theoretical categories:
(1) Labor problem: developers now experience employment threat, loss of job security, layoffs, new levels of worry about the future
(2) Identity problem: developers used to feel special because generating code was placed on a cultural pedestal (sign of a special third brain lobe or whatever), that perceived specialness was a pillar of our personal identity, and now our egos are bruised because machines can do it and we don’t feel special anymore
While there’s doubtless truth to both of those in some / many cases, I posit a third theory:
(3) Purpose problem: contrary to popular belief, developers actually care quite a lot about the people who use our software and we derive a sense of purpose and meaning from doing what we believe to be good work; the current environment undermines that, not just LLMs but LLMs as part of a broader vortex of enshittification, and our world is effectively saying “everything you cared about doesn't matter, you can't hope to fight to make it matter, and you are stupid for caring”
I think there's evidence for that last theory in the kinds of despair you hear from developers: not just anxiety about paying the bills, not just angry feather-puffing, but a kind of existential despair that comes from the unraveling of one’s internal sense of purpose and meaning.
4/3
@inthehands I was waiting for an AI system which parsed my whole code, created a symbolic representation of not only the code but also its environment and even meaning extracted from comments, and used precise symbolic logic to locate and fix mistakes.
What we got instead with LLMs was a fuzzy pattern matcher which guesses what your code is doing based on something similar it saw on its training set, and outputs plausible code by merging samples it saw during training.
It has its uses, but...
-
Put more concisely:
I’d bet money that developer reaction to LLM-driven development would be •very• different if its practical effect were to force management to slow down development and sink more money into quality.
5/3
Yes. “Moral injury” is indeed a relevant concept here.
-
@inthehands In a related vein I read this the other day and thought it was good
https://ryancheley.com/2026/08/17/what-if-maintainer-burnout-isn-t-burnout/
Saw and appreciated that too, and yes, it's another part of the picture for sure.
-
The software in question is Arbiter Sports (arbitersports.com).
The headliner among the •numerous• software flaws I encountered in this single registration process: the site fails form validation when making subsequent edits — or no edits, just resaving unchanged! — to a form that the system •had already accepted•.
The only user-visible message is “Required Information Missing.” (There was no required info missing; again, it already passed validation.) The problem, visible only in the Javascript console, was that the site was rejecting non-alphanumeric characters in a phone number it had pulled from its own database.
The fix was to make some keystrokes in the offending field to force the site’s Javascript to re-sanitize it for the back end.
2/3
@inthehands Impressive. And a bit beyond the capabilities of users who aren't computer science professors!
And d.u.m.b beyond words on the part of the registration software.
-
@inthehands Here is a good faith argument in favor of AI assisted coding. We, the blind community, have been asking for years to make accessibility a priority in software development. For decades we've heard "it’s not on the roadmap". So we decided, with the help of AI, to take matters into our own hands.
@ysotomayor @inthehands That was always possible by building new tools or extending old ones -- and that applies to all sorts of goods that haven't existed but could.
AI makes those things feasible via plagiarism, which was also always possible - just not allowed.
AI just makes that plagiarism more accessible to people that don't have the skills to build those new tools or to extend old ones.
-
Number 3 is me.
I've been writing my software for 23+ years. As an employee, a contractor, and then as a partner with a larger percentage of ownership each year until I owned it all.It's my baby, it feeds the employees in my tiny company, and runs the businesses of my ~85 clients.
I'm going out of my way not to enshitify our product, and to continue to provide quality and value, and I'm not going to let LLMs near our code (for both the ethical and technical reasons).
The ethical things are the big ones for me but for a long time I thought LLM dev just wasn't a way to make software you can stand over.
Then I get a job somewhere that it's used every day.
Now I KNOW it's not a way to make software you can stand over.
I could tell you stories but I would need several drinks.
-
Put more concisely:
I’d bet money that developer reaction to LLM-driven development would be •very• different if its practical effect were to force management to slow down development and sink more money into quality.
5/3
@inthehands
Software was troubled before LLMs offered to fix it. Many have enumerated the causes but all seem beyond repair. I’ve offered my solutions which all seem dated. One has only ask, who benefits from the disfunction? -
@inthehands
Software was troubled before LLMs offered to fix it. Many have enumerated the causes but all seem beyond repair. I’ve offered my solutions which all seem dated. One has only ask, who benefits from the disfunction?That’s a good question, and it’s a sociopolitical and economic question.
-
Put more concisely:
I’d bet money that developer reaction to LLM-driven development would be •very• different if its practical effect were to force management to slow down development and sink more money into quality.
5/3
@inthehands As an added note; The labour issues were starting to grow as a problem anyway - we passed the point where "Learn to code" was a path to a stable career before the slop, as far as I can tell;
and the identity issues... really, how can you have that much of an ego about it when you occasionally get outdone by - or seriously work alongside in the FOSS side of things - a literal child or teenager, who's not even out of grade school yet? -
OK, I guess I wasn't done after all.
Much of the opining about developer backlash to LLMs falls into two loose theoretical categories:
(1) Labor problem: developers now experience employment threat, loss of job security, layoffs, new levels of worry about the future
(2) Identity problem: developers used to feel special because generating code was placed on a cultural pedestal (sign of a special third brain lobe or whatever), that perceived specialness was a pillar of our personal identity, and now our egos are bruised because machines can do it and we don’t feel special anymore
While there’s doubtless truth to both of those in some / many cases, I posit a third theory:
(3) Purpose problem: contrary to popular belief, developers actually care quite a lot about the people who use our software and we derive a sense of purpose and meaning from doing what we believe to be good work; the current environment undermines that, not just LLMs but LLMs as part of a broader vortex of enshittification, and our world is effectively saying “everything you cared about doesn't matter, you can't hope to fight to make it matter, and you are stupid for caring”
I think there's evidence for that last theory in the kinds of despair you hear from developers: not just anxiety about paying the bills, not just angry feather-puffing, but a kind of existential despair that comes from the unraveling of one’s internal sense of purpose and meaning.
4/3
@inthehands Yes, absolutely tagging myself as 3 here. Nicely expressed, thank you.
-
@inthehands As an added note; The labour issues were starting to grow as a problem anyway - we passed the point where "Learn to code" was a path to a stable career before the slop, as far as I can tell;
and the identity issues... really, how can you have that much of an ego about it when you occasionally get outdone by - or seriously work alongside in the FOSS side of things - a literal child or teenager, who's not even out of grade school yet?I mean, there are some absolutely absurd egos in the tech world, so. But big picture yes.
