There was one of those "memes" a few years ago that is just a screenshot of someone's Twitter post that was essentially:
"My wife is a teacher, she used AI to help create an assignment, all the kids used AI to complete it, and now she's using AI to grade it. Nobody learned anything, nobody really did anything. What's happening?"
Being the devil's advocate, it sounds like no one involved see any value in that exchange, therefore they don't care.
In that sense AI slop is a symptom, not a disease. But perhaps also a catalyst.
I really wonder if there is a sort of silver lining here, and in the long term low value activities will be filtered out of society. Though that borders on the AI maximalist view which I don't fully agree with.
Of course the glaring question is what value even is.
What makes you think the government is remotely qualified to run a canning operation, a logistics operation, a warehousing operation, an HR operation, and a finance operation for peaches?
Also which government? Because there are at least 3-5 relevant ones here, maybe more.
>What makes you think the government is remotely qualified to run a canning operation, a logistics operation, a warehousing operation, an HR operation, and a finance operation for peaches?
That'd actually be quite easy for this particular federal government actually (current administration aside). And probably California too.
> What makes you think the government is remotely qualified to run a canning operation, a logistics operation, a warehousing operation, an HR operation, and a finance operation for peaches?
The DoD (for one) runs lots of logistics, warehousing, HR (2.8M), and finance stuff.
Have you ever looked at the prices they pay? Government is the last place I'd look for competent management, anyone good/noncorrupt would be making 10x in the private sector.
The government is able to do all of this for an entire literal army of people, spread across the entire world. And for an additional smaller army we call the Marines. Only difference is we add peaches on top of the canning of lead.
I'm not saying this is a good idea, but the government doesn't need to know how to micromanage these operations. The company already has employees who can do these things. All they need is to get paid. If the government decided that the final harvest of peaches needed to be canned, they could take over the business and pay to make it happen.
edit: Actually, they don't even need to take over the business. Another company is already operating it. The government could simply sign a contract to buy the 50,000 tons of canned peaches and the company would can them. Again, not to endorse the idea, but it is very straightforward logistically.
If nobody else wants to buy 50,000 tons of canned peaches, why should the government use other people's tax revenue to buy those peaches? Why not just get rid of them (which is what we're doing)?
I never said the government should buy the peaches. I pointed out that your argument didn't work.
You said the government shouldn't do this because they lacked the expertise and (implicitly) would balls it up. I pointed out that it didn't require any expertise. That is all.
It seems closer to "roll two or three successive 1s on a D100 and have your LLM hooked directly into your production systems and have your LLM user have DELETE permissions" and probably 1 or 2 other things I'm forgetting.
It pulled an api key from an unrelated file. It wasn’t given delete permission, it found it.
Not picking on you specifically, but in general the comments here have me wondering if AI has stolen our basic reading comprehension, or if we were always this bad.
Anyway, take “LLM user had delete permission” off your list and add “deleting the production db also deletes all the backups” to the list.
There really shouldn't be any "serious and unfixable way" to break things, especially in a modern company that uses technology in any meaningful way. The fact it's even possible to get into an unrecoverable state is the primary issue.
> Why does any of this imply they should become a regulated utility?
Because the majority of the HN crowd defaults to "a massive government bureaucracy would do this better" unless it's even tangentially related to their industry in which case it's "regulations bad" and "move fast break things."
It's also not tautological that React apps have bad error handling. You can do proper error handling and retry logic in React, and I can't for the life of me understand why GitHub engineers making several hundred thousand a year in cash and at least that much in stock simply... don't?
It's no wonder my jobs feed is flooded with senior engineering positions at GitHub (one wonders if they're growing, or jettisoning dead weight) but I can't imagine it's a good look for the resume to put GitHub on it at this point.
What's hilarious about that script is that the solution is so simple: use a less-than comparison instead of an equals. That's really, really all it would have taken to fix the issue. And yet https://github.com/actions/runner/pull/3157 was opened on 2024-02-17 and was merged on 2025-08-21, a full 18 months (plus a few days) later! It took literally 18 months for them to merge a bugfix that is trivially obvious to see is correct.
Yeah, the problems at GitHub ran (and still run) deep.
P.S. Yes, there are busy-wait issues in that code, which should have been addressed by bringing back the check for the `sleep` command and using it if available, falling back on the CPU-burning busy-wait only if `sleep` was unavailable. But the most revealing thing is the 18 months to merge a trivial-to-verify PR. That, more than the bad busy-wait loop, is the fundamental indicator of brokenness at GitHub under Microsoft's ownership.
When is the "get better" step? I've only ever seen two things happen mid- or post-enshittification:
1. The company builds a moat and just remains shit.
2. New entrants either displace the company entirely (most likely) or competition slows the enshittification process (distant second) or reverses it (almost never).
It's not clear to me why "get shitty" is a necessary step to this. What part of GitHub's executives' grand plan is "have a barely-functional service that randomly prevents people from working"?
> What part of GitHub's executives' grand plan is "have a barely-functional service
What about lock-in, being a monopoly? Why wouldn’t you maximize on saving costs? Sure some people leave, but the majority is not going anywhere. And if the platform dies they’ve made more money than to keep it alive.
The enshittification process milks the current product of all of the money that can be wrung from it by any means just shy of immolation.
Companies aren't getting cheap loans right now so they're desperate to juice their stocks so that upper management can secure their bonuses.
That's why "get shitty" is necessary.
When they've wrung it dry, pocketed all of the crumbs of raw cash they can get, then they'll either collapse due to overmilking their products or they'll realize that the only way to refatten the calf is to bring in new customers, so they'll unshittify it for the fresh infusion of customer money.
It's a cycle, and one I predict will inevitably lead to many of these companies' collapse.
reply