411
Devs gripe about having AI shoved down their throats (www.theregister.com)
submitted 3 days ago by brianpeiris@lemmy.ca to c/technology@lemmy.world
42 comments fedilink hide all child comments
top 42 comments
sorted by: hot top controversial new old
[-] HazardousBanjo@lemmy.world 19 points 2 days ago

As per usual, those pushing for AI the most are the ones who don't fucking use it.

Is AI good for printing out the syntax, or an example of a library you haven't used before?

Sure, sometimes yes. Sometimes no.

Should it be a requirement to be a regular part of software development?

No. AI hallucinates very often and is imitative in nature, not innovative.

[-] chilicheeselies@lemmy.world 2 points 1 day ago

More generally, noone should be required to do anything particular until it affects the team. Forcing people to work a certain way is beyond stupid.

[-] floofloof@lemmy.ca 149 points 3 days ago

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

[-] gravitas_deficiency@sh.itjust.works 50 points 3 days ago

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.

[-] acosmichippo@lemmy.world 34 points 3 days ago

you could probably even get copilot to write it!

[-] brsrklf@jlai.lu 30 points 3 days ago

"Prompt yourself with some bullshit so that it looks like you're doing something productive."

Who knows, maybe that's how you attain AGI? What is a more human kind of intelligence than looking for ways to be a lazy fuck?

[-] queerlilhayseed@piefed.blahaj.zone 24 points 3 days ago* (last edited 3 days ago)

Prompt an LLM to contemplate its own existence every 30 minutes, give it access to a database of its previous outputs on the topic, boom you've got a strange loop. IDK why everyone thinks AGI is so hard.

[-] tias@discuss.tchncs.de 4 points 3 days ago

Not when you have to do SAML authentication to get a token for your AD account first.

[-] brsrklf@jlai.lu 3 points 2 days ago

Unless you know that guy working on both API management and the identity provider.

If, hypothetically, someone came to that person with a problem like that, they might do it just for fun. Allegedly.

[-] fibojoly@sh.itjust.works 2 points 1 day ago

That person and I seem to be doing similar jobs because I certainly would take on that challenge (SAML is such a fucking nightmare...)

[-] Evotech@lemmy.world 1 points 2 days ago

You can even schedule it within copilot

[-] python@lemmy.world 15 points 2 days ago

I've been refusing to use any AI tools at all and luckily my manager respects that, even if he uses AI for basically everything he does. If the company ever decides to mandate it I'll just have the AI write all my code and commit it with no checks. With the worker's rights here, it'll take several months to fire me anyways.

[-] punrca@piefed.world 76 points 3 days ago

The software engineer acknowledged that AI tools can help improve productivity if used properly, but for programmers with relatively limited experience, he feels the harm is greater than the benefit. Most of the junior developers at the company, he explained, don't remember the syntax of the language they're using due to their overreliance on Cursor.

Good luck for the future developers I guess.

companies that've spent money on AI enterprise licenses need to show some sort of ROI to the bean-counters. Hence, mandates.

Can't wait for AI bubble to pop. If this continues, expect more incidents/outages due to AI generated slop code in the future.

[-] scarabic@lemmy.world 9 points 3 days ago* (last edited 3 days ago)

From what I see, the current is beginning to turn a little toward valuing senior devs more than ever, because they can deal with the downsides of AI. Junior devs, on the other hand, cannot, and their simpler coding work is also more easily replaced by AI. So we’ll see fewer junior dev jobs, but seniors might do fine. I’m not sure that’s good news for the profession as a whole, but its been an extremely long gold rush into software and online services so some correction probably won’t be the end of the trade.

Oh and yes senior devs are still hounded to use AI, because it will get them further, faster. And there are no more junior devs to help. In the hands of a skilled dev, AI tools can be powerful, and they can spare some toil, and help them find their feet in less familiar frameworks and in foreign codebases.

[-] dreadbeef@lemmy.dbzer0.com 2 points 1 day ago* (last edited 1 day ago)

Code is the easiest thing as a dev. AI wont help me because Im already a good coder. Its the interconnectedness between services, dependencies in ownership (who do I talk to when a gateway error occurs vs a a 401 or 403 etc), etc that are the hard problems. Getting the right people together to solve the thing, you know? AI doesnt fix that.

[-] aesthelete@lemmy.world 26 points 3 days ago* (last edited 3 days ago)

The problems in software still remain the same though:

(1) Bureaucracy

(2) Needless process

(3) Pointy headed managers

(4) Siloed teams

(5) Product people who have no idea what they want to build

(6) Shitty, poorly performing legacy code nobody wants to touch

Honestly, AI is just the latest thing that can boost your productivity at starting up some random app. But that was never the difficult part anyway.

[-] squaresinger@lemmy.world 16 points 3 days ago

This, so much this.

When I think about what limited my performance in the last year it was mostly:

  • Having to get 5 signatures before I am allowed the budget to install some FOSS software on my work PC that the corporation has already approved for use on work PCs
  • Spending 8 months working on a huge feature that was scrapped after 8 months of development
  • Being told that no, we cannot work on another large feature request (of which there are many in the pipeline) because our team said we can only fit that scrapped feature into this year and we are not allowed to replan based on the fact that the feature we were supposed to work on got scrapped by business

And then they tell us to return to office and use AI for increasing efficiency.

It's all an elaborate play performed by upper management to feign being in control and being busy with something. Nobody is actually interested in producing a product, they all just want to further their own position.

[-] Valmond@lemmy.world 2 points 3 days ago

The problem is the N+2 is in on it too. And so on. "It just works!"

[-] scarabic@lemmy.world 1 points 2 days ago

We are pushing our product managers to communicate their requirements with live prototypes rather than PRDs and mockups. It forces them to actually think their ideas through, and even allows them to get some hallway feedback before even bothering an eng. This might help with #5. But I’ve never had sympathy for engineers who think all the process around them is net negative, because nothings ever stopped engineers from striking out on their own, without all that, and making great businesses. If your PM and VPs are bringing you down, go it alone. If you can’t pull that together into a paycheck then maybe it’s not all as useless as some say.

[-] aesthelete@lemmy.world 4 points 2 days ago* (last edited 2 days ago)

But I’ve never had sympathy for engineers who think all the process around them is net negative, because nothings ever stopped engineers from striking out on their own, without all that, and making great businesses.

Not all process is pointless, but needless process by definition is. There are also a shit ton of things that stop engineers from "striking out on their own".

If your PM and VPs are bringing you down, go it alone. If you can’t pull that together into a paycheck then maybe it’s not all as useless as some say.

The whole talk of "go[ing] it alone" kinda strikes me as "bootstrapping", libertarian non-sense.

I don't want to do marketing, sales, finance, legal, and product bullshit myself. That's why I'm an employee.

Two things can be true at the same time, for instance, a company can have a lot of bloated, needless process that stifles people and still pull in enough money to be able to pay for their employees to live a life.

With the amount of market concentration there is in every sector as far as the eye can see, nearly every software-producing company has a cash cow of some sort, and then has a bunch of complete money losers that are subsidized by that cash cow.

So, it's completely possible that the company overall fully sucks and hasn't developed anything new of value to someone in decades, but the legacy business keeps the miserable employees from the bread line.

To return to the point, AI doesn't solve any of this or even help with it.

[-] brsrklf@jlai.lu 100 points 3 days ago* (last edited 3 days ago)

Nothing tells that AI is a clever use of your ressources like enforcing a mandatory AI query quota for your employees, and having them struggle to find anything it's good at and failing.

[-] WanderingThoughts@europe.pub 19 points 3 days ago

So, it's a DAI requirement

[-] jjjalljs@ttrpg.network 12 points 2 days ago

Managers are often idiots in over their heads. AI is really aggravating that problem.

[-] phutatorius@lemmy.zip 7 points 2 days ago

My team have been trying it. So far, at best, it costs money but makes no difference in outcomes. Any productivity gains are wiped out by the time needed to diagnose and correct the errors it introduces.

I'd use Clippy before I use any of that time-wasting, unreliable, energy-guzzling crap.

[-] jonathan7luke@lemmy.zip 43 points 3 days ago

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

[-] melsaskca@lemmy.ca 1 points 1 day ago

This is just history repeating itself. A while ago it was typewriter repair persons vs. the keyboard. New tech won and time marched on. Having said that...fuck AI.

[-] Septimaeus@infosec.pub 33 points 3 days ago* (last edited 2 days ago)

I’ll admit, some tools and automation are hugely improved with new ML smarts, but nothing feels dumber than hunting for problems to fit the boss’s pet solution.

[-] tyler@programming.dev 6 points 3 days ago

Like what?

[-] assaultpotato@sh.itjust.works 21 points 3 days ago

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.

[-] MangoCats@feddit.it 5 points 3 days ago

Agree, I've been using claude extensively for about a month, before that for little stuff for about 3 months. It is great at little stuff. It can whip out a program to do X in 5 minutes flat, as long as X doesn't amount to more than about 1000 lines of code. Need a parser to sift through some crazy combination of logic in thousands of log files: Claude is your man for that job. Want to scan audio files to identify silence gaps and report how many are found? Again, Claude can write the program and generate the report for you in 5 minutes flat (plus whatever time the program takes to decode the audio...)

Need something more complex, nuanced, multi-faceted? Yeah, it is still easier to do most of the upper level design stuff yourself, but if you can build a system out of a bunch of little modules, AI is getting pretty good at writing the little modules.

[-] Septimaeus@infosec.pub 6 points 3 days ago* (last edited 3 days ago)

For example the tools for the really tedious stuff, like large codebase refactoring for style keeping, naming convention adherence, all kinds of code smells, whatever. Lots of those tools have gotten ML upgrades and are a lot smarter and more powerful than what I remember from a decade ago (intellisense, jetbrains helper functions, various opinionated linter toolchains, and so forth).

While I’ve only experimented a little with some the more explicitly generative LLM-based coding assistant plugins, I’ve been impressed (and a little spooked) at how good they often were at guessing what I’m doing way before I finished doing it.

I haven’t used the prompt-based LLMs at all, because I’m just not used to it, 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 damn useful.

I’ll integrate the prompt-based tools once I can host them locally.

[-] MangoCats@feddit.it 4 points 3 days ago

In the work I have done with Claude over the past months, I have not learned to trust it for big things - if anything the opposite. It's a great tool, but - to anthropomorphize - it's "hallucination rate" is down there with my less trustworthy colleagues. Ask it to find all instances of X in this code base of 100 files of 1000 lines each... yeah, it seems to get bored or off-track quite a bit, misses obvious instances, finds a lot but misses too much to say it's really done a thorough review. If you can get it to develop a "deterministic process" for you (shell script or program) and test that program, then that you can trust more, but when the LLM is in the loop it just isn't all there all the time, and worse: it'll do some really cool and powerful things 19/20 times, then when you think you can trust it it will screw up an identical sounding task horribly.

I was just messing around with it and I had it doing a files organization and commit process for me, was working pretty good for a couple of weeks, then one day it just screwed up and irretrievably deleted a bunch of new work. Luckily it was just 5 minutes of its own work, but still... that's not a great result.

[-] BackgrndNoize@lemmy.world 23 points 3 days ago

These scummy fucks even put it as a requirement in job descriptions these days

[-] MonkderVierte@lemmy.zip 29 points 3 days ago

This is a red flag for corpo culture shenanigans. Dodge the bullet.

[-] floofloof@lemmy.ca 10 points 3 days ago

What even is the requirement? "Must be able to ask a chatbot to do stuff"?

[-] supersquirrel@sopuli.xyz 23 points 3 days ago* (last edited 3 days ago)

Then unionize! Nothing else will stop this.

[-] phil@lymme.dynv6.net 12 points 3 days ago* (last edited 3 days ago)
[-] floofloof@lemmy.ca 25 points 3 days ago

And it won't be the rich that get hurt when the AI bubble bursts. It will be us.

[-] brianpeiris@lemmy.ca 6 points 3 days ago

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.

[-] devfuuu@lemmy.world 5 points 3 days ago

Unions is not really a concept that is available to devs. At least around here.

[-] Forbo@lemmy.ml 1 points 2 days ago

I just attended an organizer training, and 70% of the people there were devs. Don't believe the corporate bullshit, unions are for everyone.

this post was submitted on 20 Nov 2025
411 points (100.0% liked)

Technology

77022 readers
1775 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws