Submitted 6 hours ago by brianpeiris@lemmy.ca to technology@lemmy.world
https://www.theregister.com/2025/11/19/ai_force_feeding/
“We were still required to find some ways to use AI. The one corporate AI integration that was available to us was the Copilot plugin to Microsoft Teams. So everyone was required to use that at least once a week. The director of engineering checked our usage and nagged about it frequently in team meetings.”
The managerial idiocy is astounding.
It’s pretty easy to set up a cron job to fire off some sort of bullshit LLM request a handful of times a day during working hours. Just set it and forget it.
you could probably even get copilot to write it!
Nothing tells that AI is a clever use of your ressources like making a mandatory AI query quota for your employees, and having them struggle to find anything it’s good at and failing.
So, it’s a DAI requirement
For the FAANG companies, they do it in part so they can then turn around and make those flashy claims you see in headlines like “95% of ours devs use [insert AI product they are trying to sell] daily” or “60% of our code base is now ‘written’ by our fancy AI”.
These scummy fucks even put it as a requirement in job descriptions these days
This is a red flag for corpo culture shenanigans. Dodge the bullet.
I’ll admit, some tools and automation are hugely improved with new ML smarts, but nothing feels dumber than finding problems that fit the boss’s solution.
Like what?
claude performs acceptably at repetitive tasks when I have an existing pattern for it to follow. “Replicate PR 123, but to add support for object Bar instead of Foo”. If I get some of this busy work in my queue I typically just have claude do it while I’m in a meeting.
I’d never let it do refactors or design work, but as a code generation tool that can use existing code as a template, it’s useful. I wouldn’t pay an arm and a leg for it, but burning $2 while I’m in a meeting to kill chore tasks is worth it to me.
For example the tools for the really tedious stuff, like large codebase refactoring for style keeping and naming convention adherence, those tools have become a lot more powerful than what I remember from a decade ago.
While I’ve only experimented a little with some the more explicitly generative LLM-based coding assistant plugins, I was impressed (and a little spooked) at how good they often were at guessing what I was doing way before I finished doing it.
I haven’t used the prompt-based LLMs at all, but I’ve watched nearby devs use them for stuff like manipulating a bunch of files in a repeated pattern, breaking up a spaghetti method into reusable functions, or giving a descriptive overview of some gnarly undocumented legacy code. They seem pretty useful, but I don’t think I’ll be able to use them fluidly until I can host them locally.
Then unionize!
A bit of patience, the burst of that bubble comes… (forbes.com/…/ai-bubble-may-pop---wiping-out-40-tr…)
And it won’t be the rich that get hurt when the AI bubble bursts. It will be us.
I’d like the bubble to be true so that we can move past this nonsense phase, and it may well be true, but I could also see it being extended for years potentially, since there’s so much money being pumped into it, and governments are also buying into the hype.
Unions is not really a concept that is available to devs. At least around here.
No need to unionise when you have the power to make a startup.
But then first you need the power and ability to make a startup.
punrca@piefed.world 1 hour ago
Good luck for the future developers I guess.
Can't wait for AI bubble to pop. If this continues, expect more incidents/outages due to AI generated slop code in the future.