Fuck AI

Form a small company with colleagues. Call it UnSlopify.

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

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.

Apocalyptic times for engineers.

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

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.

"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."

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?

Seems like exactly the wrong way to use AI.

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 designation 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

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

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

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.

Just mark everything it produces as perfect

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."

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.

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.

Is this a Canadian bank?

@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.

My way of doing this is to work it by hand then have AI commit it and cut a PR.

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.

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.

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.

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.

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.

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.