this post was submitted on 08 Jul 2026
550 points (99.6% liked)

Fuck AI

7594 readers
1637 users here now

"We did it, Patrick! We made a technological breakthrough!"

A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.

AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.

founded 2 years ago
MODERATORS
 

Pointless rant. Please ignore. I'm a software developer and we all know how AI has changed our industry. How we work or why we're fired and why we can't afford PCs.

Anyways, we're already all forced to use AI already and we're already atrophying the minds of our juniors. It's great.

New team meeting and one of our managers tells us that we're never going to write code anymore at all. The AI will read the JIRA ticket and create the pull request (change request to the codebase) on GitHub. Our job is to only review the code on GitHub and then rank how well AI did and then comment and then get AI to fix it. We have to do this so we can improve the AI process. Which is funny because none of the people who plan this AI shit are data scientists. The only way they can change things is by promoting, it's not like we're releasing our own coding models but anyways ... He's like, now you should be able to do much more work and just review PRs all day now and that we should never be doing only one thing. You can only tell AI through a GitHub comment to fix a mistake and then you can start reviewing the next thing.

We were like, if it's a simple fix why can't we just fix it?

"Because we need to improve the AI process"

But then, I have to context switch.

"Yes that's the point you can come back to it later"

Why come back to it later when we can solve it now? We can even use AI to solve it now.

"No, we want you just comment on the PR so the bot can handle it"

Context switching is free apparently... It's actually infuriating because apparently we're not using IDEs any more. I personally use the GitHub plugin to review PRs in my IDE but no one else seems to do it so I don't think they even took that into account.

These guys have auto merged AI code that's taken us weeks to unravel and which we still haven't fully been able to fix. They just merge shit all the time and a lot of it is fucking slip. AI merged hundreds of tests and no one cares when they break. They didn't configure prettier because AI doesn't use it so it breaks out formatting when humans do it.

I ranted to my own manager for 30 minutes about it today and he was just as upset because every developer is now asking what exactly are they doing. My manager asked me what I would do. I said the process sucks but what are we supposed to do as devs. If I review 20 PRs a day, how is the company going to ensure my skills are gonna be sharp? What are we doing about taking in ideas from regular devs? How do we ensure code ownership when we're just merging tickets we don't write and code we had no hand in shaping?

Sorry. I actually thought I had faith in my company with AI because they were coming up with thoughtful approaches but it seems like utter incompetence.

top 50 comments
sorted by: hot top controversial new old
[–] SnarkoPolo@lemmy.world 7 points 1 day ago* (last edited 22 hours ago)

In sociology, we call it McDonaldization. By reducing a job to a series of fixed, repeatable steps, they can pay less.

[–] ilinamorato@lemmy.world 42 points 1 day ago (1 children)

"Where's the fix for ticket #6618?!?"

"Sorry boss, the AI hasn't gotten it right yet."

"You said it was a quick fix!"

"For a human it would be. But we're on infinite monkey time now. It may never be done."

[–] SaveTheTuaHawk@lemmy.ca 4 points 1 day ago

"It was the best of times...it was the blurst of times"

[–] SaveTheTuaHawk@lemmy.ca 6 points 1 day ago

Form a small company with colleagues. Call it UnSlopify.

[–] Strider@lemmy.world 4 points 1 day ago

It sucks, I feel you. I'm also in tech but changed jobs and got lucky.

Anyhow, wing it. Nobody cares. Take care of yourself.

[–] SCmSTR@lemmy.blahaj.zone 11 points 1 day ago

Lol why are you training it? You're a software dev with a product, not ai qa. Wild times we're in. Should really just cut your losses and gut all ai and go back to where you were before it. If you can't do that, then your company no longer has a purpose.

[–] quick_snail@feddit.nl 21 points 1 day ago* (last edited 1 day ago)

Sounds like a plan to make tech debt skyrocket and make productivity tank.

If I were you, I would start looking for another job. And, once you get an offer, tell them in your resignation letter why: you see the company is going to crash compared to its competitors due to wasteful use of AI and the loss of productivity that comes with it

[–] aesthelete@lemmy.world 14 points 1 day ago

Seems like exactly the wrong way to use AI.

[–] sobchak@programming.dev 12 points 1 day ago (1 children)

We have to do this so we can improve the AI process.

I'm curious what they mean by this. Are they just clueless about how anything works? Maybe AI companies are signing contracts with companies to upload all their code, data, traces, etc; so that the AI companies can improve their models? I.e. companies are acting like reinforcement tuning contractor firms for AI companies?

[–] monotremata@lemmy.ca 3 points 1 day ago

Are they just clueless about how anything works?

That's certainly how I read it. They seem to think that if you feed the LLM a new prompt that tells it it made a mistake, it'll update itself to avoid that mistake in the future. Which isn't how any of this works, but I can understand why they wouldn't know that given the marketing from the big AI companies.

A couple of years from now everyone will know this was really dumb, but right now only the engineers know that, and management won't listen to them. I guess they'll learn the hard way.

[–] mirshafie@europe.pub 3 points 1 day ago

Apocalyptic times for engineers.

[–] bitjunkie@lemmy.world 24 points 1 day ago (1 children)

Run like fifty agents in parallel and get lauded for how "productive" you are while you find another job and hopefully before they get the bill.

load more comments (1 replies)
[–] 73QjabParc34Vebq@piefed.blahaj.zone 210 points 2 days ago (5 children)

Now seems like the point for you to realise your boss doesn't care about the code base, your company doesn't, you shouldn't either. Don't get upset over work, it's just work. If the company wants to fuck themselves over, let them, help them.

You can also do some malicious compliance stuff. You can't write code? Great, take 3 weeks on every PR and do hundreds of prompts. Make the context as big as possible, burn as many tokens as you can.

Give the company what it wants, a shit code base and a massive bill.

[–] sin_free_for_00_days@sopuli.xyz 131 points 2 days ago (2 children)

I think it was the author Henry Miller who said of working,"Do exactly what they tell you and let them live to regret it."

[–] Quetzalcutlass@lemmy.world 45 points 2 days ago

But get it in writing first.

load more comments (1 replies)
load more comments (4 replies)
[–] smeenz@lemmy.nz 4 points 1 day ago

Ahhh, here comes the great filter. The Fermi paradox is solved.

[–] brucethemoose@lemmy.world 32 points 2 days ago* (last edited 2 days ago) (6 children)

@lobut@lemmy.ca

We have to do this so we can improve the AI process.

...To be clear, does this manager think y'all are "improving" the model with feedback? Like it will learn or train off your comments?

Or what? Are they just talking about the intermediate steps to the LLM API?

I'm just trying to wrap my head around this.

load more comments (6 replies)
[–] laranis@lemmy.zip 15 points 1 day ago

More doorman fallacy bullshit from idiots who couldn't develop their own thought if they were on fire.

"Gemini! It burns! Help, what should I do?! Answer with urgency and you must get it right. My skin is literally melting from my face right now. And optimize to use as few tokens during the processing as possible."

[–] helvetpuli@sopuli.xyz 35 points 2 days ago

This happened at our shop fifteen years ago. We were instructed to outsource everything to offshore.

That didn't work at all, because with a few rare , bright exceptions the people the offshore company have us could only achieve an outcome if they had a list of steps for that specific thing.

It's going to be exactly the same thing with vibe coding. It kind of works in the hands of somebody with a deep understanding of the tech, but they expect to hand it to juniors and get good result.

So we'll either have to pick up the pieces or let them flounder.

[–] Voroxpete@sh.itjust.works 73 points 2 days ago (1 children)

This is a "Cover your ass and wait for the fireworks" scenario. Get every stupid request in writing. Document everything you do. When it all blows up in their faces, be ready to roll up your sleeves and start unfucking the mess (but only if they're paying for the overtime).

You will not convince them this is a bad idea as long as it appears to be working. In IT and software dev we're all engineers; we like to fix things, so our instinct is always to try to at least make a bad process work better. Fight that instinct. Follow their stupid instructions to the letter. You want this to fail as quickly as possible so that you have hard data to point to.

load more comments (1 replies)
[–] bagsy@lemmy.world 38 points 2 days ago (3 children)

If I were you, I would burn soooo many tokens. This is a malicious compliance dream scenario.

Fuck the owner class, get paid, and watch it all burn.

load more comments (3 replies)
[–] TootGuitar@sh.itjust.works 122 points 2 days ago (15 children)

Software developer w/ 25+ years of experience here. My condolences, this sounds like a shitty situation. But it’s definitely not the first time I’ve heard a story like this.

To be perfectly honest, my professional opinion is that if we can’t, as an industry, get away from the “all AI all the time” mode of operation you describe here, we are completely fucked.

I’m looking to retire early anyway, so I will likely get out soon. But I feel awful for young engineers who don’t have that luxury, and who will be expected to maintain AI-written spaghetti code without having the years of experience writing and understanding complex code using their own brains.

load more comments (15 replies)
[–] NM_Gringo@lemmy.world 26 points 2 days ago (1 children)

I'm having early 2000s flashbacks. Overseas developers were going to replace us all for a fraction of the cost. We had to turn over our code...almost like training AI. That lasted until the first SQL server update that broke, literally, everything they did. Then they wanted a huge amount of money and weeks to get it working again. That really put management in a bind because they told us not to touch their code. Ooookay, fine. Meanwhile, I'm looking at 2,000 character URL string containing the database admin account and password in plain text.

load more comments (1 replies)
[–] ryanvade@lemmy.world 21 points 2 days ago (1 children)

I'm in the same position as you. The Devs job is now to write specfiles which Claude implements. It's been months since I wrote code myself and I'm already forgetting basics. This industry is fucked.

load more comments (1 replies)
[–] prole@lemmy.blahaj.zone 28 points 2 days ago (6 children)

In case it wasn't already clear to you, they're having you train the AI so it can literally take your job and they can lay you off.

load more comments (6 replies)
[–] ech@lemmy.ca 93 points 2 days ago (1 children)

We have to do this so we can improve the AI process.

Their end goal is all LLM, no humans. Whether it's feasible or not is irrelevant - anyone staying on is working against their own self-interest.

load more comments (1 replies)
[–] mojofrododojo@lemmy.world 67 points 2 days ago (1 children)

It's not a pointless rant. It's another voice of sanity in the long, sad grifting story this AI garbage has inflicted upon our species.

thanks for sharing.

load more comments (1 replies)
[–] inclementimmigrant@lemmy.world 30 points 2 days ago (2 children)

So my coworker and I discuss this all the time and we figure we're old enough to just not give two shits, follow the process, pick up a FOSS project or two to keep our skills up, and wait for the inevitable of when they figure out AI slop is killing them and then charge outrageous prices as contractors when AI2K hits.

load more comments (2 replies)
[–] auzy1@lemmy.world 5 points 1 day ago

Even with examples and docs, I spent hours 3 days ago to try to sort an issue on our side using AI.

Gave up, solved it myself better than our examples in 5 mins

[–] jaybone@lemmy.zip 43 points 2 days ago (2 children)

It’s not just you. This is happening everywhere in the industry.

Management has no idea what they are doing, and thinking this AI shit and these nonsense workflows will somehow work. I predict within the next two years there will be so much broken unfixable spaghetti code, entire large scale systems will no longer be maintainable. There will be so much confusion on even what kind of approach to take to fix this. This will be what people thought Y2K was going to be.

load more comments (2 replies)
[–] Wispy2891@lemmy.world 5 points 1 day ago (1 children)

It seems like the trend is don't even watch the code, many vs code forks for vibe coding now don't even have the coding portion, it's a giant prompt in some electron app

For example Google antigravity

Google antigravity

Or windsurf that openai almost paid 3 billion before changing idea (now renamed to something else) also became just a prompt

It's going to backfire spectacularly, approving pr by just reading them in the browser is insane

One thing is "I'm lazy to do this specific thing, I ask the tool to do the specific task by inserting only the useful files in context, then review manually before committing"

Another is "I write a generic prompt "add a photo sharing feature" then it directly opens a PR where another bot reads it and generates a review with so many emojis that it must good 👍🏻😊 boom merge it all the tests pass ✅ ✔️ ✅ ✔️" and then nobody actually knows what it did

Of course the ai companies prefer the second approach before without a subscription the first uses 1 cent in tokens, the second uses $100 in tokens.

[–] RedstoneValley@sh.itjust.works 52 points 2 days ago (1 children)

That's remarkably shortsighted, gullible towards the promises of AI techbros, and incredibly dumb. But fear not OP, they will learn a hard lesson or two soon. Exploding Token costs, a codebase ruined beyond repair cobbled together by a fancy autocomplete based on training data from stackoverflow in 2023... gonna be great.

I'm feel your pain, as a senior dev I decided to take a break at least till the end of the year to watch the Titanic sink in slow motion. I'm specializing in the told-you-so business right now and I'll be ready to charge premium when this ship has sunk.

load more comments (1 replies)
[–] petrichornetrainfall@piefed.social 62 points 2 days ago (3 children)

Github copilot doesn't retain anything you say in a comment, outside of the PR. It wont improve over time unless you have some process to extract comments and "learnings" out of PRs into either the org wide "copilot-instructions.md" file or into repo specific "Agent.md", "copilot-instructions.md", and "skill" files.

[–] rainwall@piefed.social 4 points 1 day ago* (last edited 1 day ago)

OP should absolutely not act on or volunteer the above knowledge.

He just needs to PR it up. They give a metric, he hits it, and can work on a coding passion project he actually enjoys in the downtime.

load more comments (2 replies)
[–] heartSagan5@lemmy.zip 6 points 1 day ago (2 children)

Ah, nothing like training your replacement. I don’t know why I try to get into IT; it’s trashed by AI/vibe coding.

I guess, right now, I’ll just maintain my private cloud, but with rsync getting vibe coding, it’s only a matter of time.

load more comments (2 replies)
[–] PeculiarGoat@lemmy.world 42 points 2 days ago (1 children)

The obvious thing to do here is let the really bad PRs through without comment, but keep the better ones in limbo with a never ending list of superfluous change requests. Fuck them both ways!

load more comments (1 replies)
[–] guitarfosec@infosec.pub 16 points 2 days ago (3 children)

Here's the question that worries me the most: Across how many critical industries is this happening, and at what scale?

It feels to me like decision makers are pushing for the creation of mountains of code no one fully understands and potentially creating massive issues with systems we can't afford to have go down. Are we creating decades' worth of technical debt in a matter of months and eroding systems that our societies need to function because people just want to save money and be part of the fad? How bad is this going to get?

load more comments (3 replies)
[–] baggachipz@sh.itjust.works 28 points 2 days ago (12 children)

We have to do this so we can improve the AI process.

Do they think that the LLM will “learn” based on feedback? If so, that’s fucking hilarious. “I had to turn the car to keep it from going off the road! Next time it will learn not to go off the road because of my teaching.”

load more comments (12 replies)
[–] SocialMediaRefugee@lemmy.world 4 points 1 day ago (1 children)

Just mark everything it produces as perfect

[–] GhostFace@lemmy.today 4 points 1 day ago

This is the way. Otherwise you're willingly investing your time into training your replacement.

These people don't care if the ai is productive right now. They just care that it's productive eventually so they can get rid of you.

[–] M1ch431@slrpnk.net 53 points 2 days ago* (last edited 2 days ago)

I think this is high-level "training your replacement" shenanigans being orchestrated by the management of your company.

What a joke.

load more comments
view more: next ›