this post was submitted on 01 Nov 2026
39 points (95.3% liked)

technology

24516 readers
337 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

founded 6 years ago
MODERATORS
 

I'm damn sure the answer is "no", but the devs at my workplace are all in on it in a way that's not as absurd on the surface as the "coding is a solved problem" kind of tech bros. There's an emphasis on the "human in the loop" that I think is far from sufficient; we used to have a human in the loop, it's called actually writing your fucking code!

As a sample, this is from a transcript of a recent discussion about AI with some devs on my team:

Me, a senior dev:

To be clear, I'm not saying not to forego the human in the loop. I'm pointing out that there is an inherent contradiction between using agent as our main means of writing code and actually being able to review all of its output -- be it before or after opening the PR. I'm worried that we'll end up in a position that we're expected to do something intractable, if not strictly speaking impossible.

New mid-level dev:

I just think we should still be responsible for reviewing all the output. Like how I see the before vs now is:

  • Before: human plan -> human write -> human review
  • Now: human plan -> claude write -> human review (+ claude review)

And in effect we're just as responsible for reviewing every line of the Al code as we were for reviewing every line of human code. Once that changes that's when the Al slop starts coming out So we should never end up posting a PR where we're like "hey guys claude wrote this so do the thing you do for claude PRs"

Team tech lead:

@AppetiteOfExcess, this is a problem across all dev teams in every industry. It's a huge issue. I think we need to lean on Al to speed up PRs, but how we do that is not well defined yet. I think it can help us get our head around a PR faster. Maybe we need to made an artifact for some PRs that give a breakdown of what is changing. Then we can grill Al once it understands the changes. That might speed things up a bit. The important thing is to really understand the code and the impact of the change.

@mid-level_dev I agree with you but I think the new process will be more like the following

  1. Humans (the whole team) plan by making highly defined stories
  2. Al makes an implementation and test plan
  3. Human reviews plan
  4. Al executes the plan with human oversight at certain steps
  5. Al does a review using /code-review (new context by default)
  6. PR is posted with change overview
  7. Human uses Al to understand the changes and review the code

I don't know how to push back on this while being taken at all seriously. It has me considering that maybe I'm in the wrong for rejecting a tool that is considered useful by all but a few stick in the mud devs, and that those devs will never have a shot at a job again unless they pull their heads out of their asses and join our modern "AI"-driven world.

top 50 comments
sorted by: hot top controversial new old
[–] TrollAccount69@lemmy.ml 2 points 1 day ago

It isn’t possible for a human being to write code responsibly.

Deepseek (the not very smart but very cheap one from China) is running a 2-3x profit on their gpu hours. That means that even with last gen tech running not generally considered very “good” models it’s still profitable to sell inference at 15 cents per million tokens in(.003 cents cache hit!) and 60 cents per million tokens out.

While the deepseek model loops and makes mistakes more than a Claude for example, when used with a harness it is equally effective if a little slower but at over ten times lower cost.

The point of this isn’t to bamboozle you with facts and jargon but to show in a clear way that what has happened in programming with llms will not go away with some bubble pop.

If you want to stay in your industry, get okay with it. I like deepseek and glm.

From the computer security side of things it has been worth it to recognize that we are currently in a triage process industry wide, that the best process will have to be fixing bugs as fast as possible no matter how and we can deal with the problems introduced by those patches later.

[–] antinutrient@hexbear.net 36 points 2 days ago (2 children)

To me the least important part about LLM code is the ability to maintain it. I don't give a fuck about the code at my job or my job or my employer. Fuck them. They're not going to keep me employed for decades, why should I make sure to create code that can be maintained for that time when it won't be me doing it. I hope my company goes out of business.

[–] hungrybread@hexbear.net 15 points 2 days ago

Thats where I'm getting too. If they want slop they can have it, its not my problem at that point.

[–] space_comrade@hexbear.net 15 points 2 days ago

Not sure what kind of work you do OP so this isn't specifically aimed at you but (hot take alert) honestly LLM code is fine for most corposlop projects. That kind of code has almost always been shit that barely worked, it was rushed and even when they gave a "senior engineer" free reign to design fancy abstractions they fall flat about 80% of the time and just make the code harder to maintain in the long run.

In my experience LLM code from latest frontier models is at least as good as the code of a developer of an average skill level.

The dumb thing here isn't AI usage it's as others have already said that devs seem to be hell bent on having themselves replaced. Use AI as much as you want and then lie through your teeth that you're actually super needed to supervise it properly.

[–] PorkrollPosadist@hexbear.net 23 points 2 days ago* (last edited 2 days ago)

I think it is possible to have ethical "LLMs", but the technology does not exist. An ethical LLM would require us to re-imagine the entire process, from data gathering, to tagging and organization, to ML training, to applications. There is no ethical application for the existing technology. (I put LLM in scare quotes, because with the required changes, you might not categorize the end result as an LLM any more, though there are broad applications for the use of machine-learning techniques on large bodies of information)

First and foremost, ethical LLM technology must be environmentally sustainable. We are in the middle of a run-away climate crisis and there is no excuse to be wasting energy like this. Everyone responsible for LLMs and proof-of-work cryptocurrency should be executed right alongside the oil execs. It must preserve attribution. It must not be a tool for crime-prediction, surveillance, and social manipulation (e.g. profile-based advertising). It must be accessible and democratic.

In my mind, instead of having software which synthesizes language (human or programming languages), it would function as a highly sophisticated search engine. You might prompt "I want to make a REST client which can speak the Matrix protocol" and based on the corpus of training material it can identify the required aspects of an implementation and source material for each required component. This would be a very useful tool, but it is not useful in the way LLMs are being deployed today, which is to steal dead labor (the corpus of free software, documentation, internet discussions, and literature in general), in order to make living labor redundant.

That said, I would make the argument that LLMs are not the core problem in software engineering. They are deeply exacerbating the actual problem which is a crisis of complexity (which is why I think using them makes you an automatic dickhead). We're sprinting into a world where we rely on essential components (the kernel or the web browser, for instance), which have completely outrun the capacity for responsible public maintenance. The deficit in maintenance is papered over by using LLM's to "accelerate" development and review duties, but this only results in even more complexity. I believe this crisis is going to reach a tipping point fairly soon, and it is completely unrelated to the financial situation of the looming AI bubble.

[–] Chana@hexbear.net 29 points 2 days ago (2 children)

Both of your coworkers' plans are to actually not review the code. They say Claude will do it. This guarantees you will get garbage and break things. They do actually have techbro misunderstandings of the reliability of these tools and perhaps a misunderstanding of how good they personally are at planning and documentation if they don't expect more iteration than one PR and review.

You should also expect the cost of tokens to skyrocket eventually, just as an operational thing.

But this brings up the real point: why is tech lead giving a shit about, "I think we need to lean on Al to speed up PRs"? Aside from that not actually being the usual outcome, it's also not their job to care about it. They are acting like C suite or management or a suck-up. "Speed up PRs" isn't a meaningful thing to anyone except the bean counters trying to create metrics of success to use to discipline labor and climb the ladder. Is team lead spending all their time on PRs? If their new job is reviewing Claude PRs (which they imply and then contradict), they'll be spending more time on that now, not less. They might do more PR reviews in less time but they'll either be reviewing for common inevitable mistakes (you cannot rely on Claude to do the review lmao) or just let garbage through and have to fix it later. Either way they're sacrificing dev time to do more review time, telling themselves it's faster but likely not tracking whether milestones are being met faster

But most importantly why are they doing managements' job. Y'alls job is to promise less to manager so you over deliver but make it sound like you're technical experts that are irreplaceable. Not sell the idea that writing and reviewing code has been automated and you gotta get your metrics up.

[–] Snort_Owl@hexbear.net 26 points 2 days ago (2 children)

But most importantly why are they doing managements' job

This bit has been baffling me as of late. Almost all software devs I know have bent over backwards to give businesses what they want. It wasnt even that long ago I was revelling in work from home and basically putting most of my day into MMOs. All ai did was enable the worst of us to bootlick harder in some shallow attempt to gain approval.

My colleagues used to mock me for leaving on time. Like its not even early i have worked my contracted hours and leave and you cant even do that??????? They continue to work 12 hour days and tell me their life feels hollow like yeah no shit

[–] MayoPete@hexbear.net 10 points 2 days ago (2 children)

Could this behavior stem from the job market being total ass? People just trying to hold onto what they have.

[–] Snort_Owl@hexbear.net 12 points 2 days ago* (last edited 2 days ago)

No the job market could be perfect the behaviour would be the same. A lot of software devs have no concept of class consciousness or solidarity and they will absolutely fuck each other over for no good reason or to just look better than someone else.

In my circle all my colleagues are commie adjacent cos I got them all unionised so we back each other up but outside of that group its the hunger games. I guess the upside of this ai crap is a decent chunk of software devs now no longer think theyre immortal against the whims of capital so maybe it will change but Im not seeing that yet. All i see today is the wish to be the last man standing which isnt very useful

[–] Chana@hexbear.net 11 points 2 days ago (1 children)

It's actually worse in the PMC STEM white collar jobs with low unemployment rates. They haven't been screwed over by management as much so they tend to believe the corpo propaganda. Plus a lot of them are the type to think Elon Musk is a smart "disrupter" or NFTs are a great investment.

[–] Snort_Owl@hexbear.net 8 points 2 days ago* (last edited 2 days ago) (2 children)

I know several people at work currently who quote Elon. A solid half of the people i work with “invest” in crypto

[–] Chana@hexbear.net 6 points 1 day ago

lmao we gotta come up with our own scams to funnel these folks' money to people who need it

[–] AppetiteOfExcess@hexbear.net 6 points 2 days ago (1 children)

My tech lead was genuinely impressed with the flying tesla stunt from a few weeks ago.

I've been wanting to try and get a more "professional" job, but every time I talk to someone about it it sounds like hell.

I'm just gonna deal with the dumb mom and pop bullshit where I'm the only person in the company with any actual computer literacy and get to set all the standards.

[–] Chana@hexbear.net 9 points 2 days ago

Live2Work Work2Die coworkers are the worst.

[–] AppetiteOfExcess@hexbear.net 11 points 2 days ago

But this brings up the real point: why is tech lead giving a shit about, "I think we need to lean on Al to speed up PRs"? Aside from that not actually being the usual outcome, it's also not their job to care about it. They are acting like C suite or management or a suck-up. "Speed up PRs" isn't a meaningful thing to anyone except the bean counters trying to create metrics of success to use to discipline labor and climb the ladder.

This mindset is rampant at my employer. Devs are well compensated enough with salary and benefits that they see their benefit as being strictly aligned with the company's. Most of my coworkers seem to have gotten into software development as a way to make money, with little or no love of the craft. Those who do get into the process love the SDLC part of the craft much more than the coding part.

[–] Snort_Owl@hexbear.net 29 points 2 days ago* (last edited 2 days ago) (3 children)

The problem is the vast majority of software engineers are charlatans who would spend 99% of their time making annoying abstractions to piss me off personally instead of solving the problem. Now expand this to ai they can make those annoying abstractions so vast and so quick that you basically need ai to delete their code as well lol. The entire thing is a solution in search if a problem that only really exacerbates the weird dogmas software devs have put in place for years. So for the most part I use this robot shit to delete all their robot shit.

If you have to use it never get it to start the work for you only use it to tidy up work you have already done yourself, write the plan and MVP and some thin docs and get it to tidy up after using abstractions you approve.

This way you know what the code is doing, keep your skills and it really only does the boring work for you and a higher tendency to get a reasonable output.

The other use is as a searcher tool for unfamiliar codebases you can get them to map it out for you or locate something you’re looking for. Since im forced to use it at work this is how I keep my delivery speed high without completely removing my brain from my skull, it gives me direct control and autonomy where ai is a searching or formatting tool at best. It also has the main target of my already working code to go on which means it spends less time doing random shit. If you can basically target it at the stuff you don’t like doing and try to keep doing what you enjoy.

This is basically the only way i have managed to “keep up” without completely losing my soul or passion for programming. I still need to work on personal projects outside of work to keep sane though and that will be relegated to human written docs, books and typing

But don’t get me wrong im the biggest ai hater here i detest the technology and what its doing. This is only if you HAVE to use it how not to hurt yourself in the process coming from someone who actually likes solving real problems instead of inventing problems to solve. And you’re not wrong for rejecting the tool because the idea a human just needs to review slop code is ridiculous but also not even what happens in practice and blindly trusting it is kicking the can down the road but also harming your own career position and typically only promoted by people who were shit a writing code.

[–] someone@hexbear.net 10 points 2 days ago* (last edited 2 days ago) (2 children)

I've always had a visceral hatred for the term software engineer itself. The only people that ought to be able to call what they do "software engineering" are people working on must-not-fail-under-any-circumstances programs like control systems for lunar landers or nuclear reactors or MRI machines. There's a good reason that "engineer" is legally reserved term in many countries, reserved for people who are members of a professional engineering licensing body and who have gone through a formal education and apprenticeship to an engineer. It shouldn't be able to be slapped on a linkedin profile because some HR lackey says that Spaghetti McVibercoder is an engineer because they know how to vomit Claude code that they don't understand into a git repo.

[–] AssortedBiscuits@hexbear.net 9 points 2 days ago (1 children)

The watering down of the term started with electrical engineers who only work with consumer electronics or mechanical engineers who only work with toys. Civil engineers have been seething about this for decades at this point.

[–] livestreamedcollapse@lemmy.ml 7 points 2 days ago* (last edited 2 days ago)

In the sciences too, 30 years ago it was molecular biologists or biochemists 'engineering' strains or enzymes but now it seems a whole layer of bioengineers has grown over those research fields doing the same things. The exception is chemical engineering, that's always just been designing the plumbing for chemical plants so they don't explode

[–] imogen_underscore@hexbear.net 4 points 2 days ago (1 children)

https://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD1036.html

A number of these phenomena have been bundled under the name "Software Engineering". As economics is known as "The Miserable Science", software engineering should be known as "The Doomed Discipline", doomed because it cannot even approach its goal since its goal is self-contradictory. Software engineering, of course, presents itself as another worthy cause, but that is eyewash: if you carefully read its literature and analyse what its devotees actually do, you will discover that software engineering has accepted as its charter "How to program if you cannot.".

[–] KuroXppi@hexbear.net 2 points 1 day ago

As economics is known as "The Miserable Science

The invention of this phrase also conveniently gets the speaker to buy in that economics is, in some way, a science, which it patently isn't

Abstractions are good sometimes, but only sometimes. LLMs seem to like abusing them like crazy though.

I'll pretty frequently use abstractions to take really abrasive APIs and make them easier to use. Specifically because I use Python, and no one ever bothers to implement the data protocols for their classes.

I shouldn't be calling resource.get_next_item() in a while loop when it should implement the iterator protocol so __next__ and __iter__ can do that work for me.

LLMs don't really seem to care about that sort of abstraction though, since it's entirely there to make my life as someone who writes code easier, and they will just happily call get_next_item over and over.

[–] AppetiteOfExcess@hexbear.net 6 points 2 days ago (1 children)

The entire thing is a solution in search if a problem that only really exacerbates the weird dogmas software devs have put in place for years.

Whenever I try to voice this at work, it falls on deaf ears. Management has cultivated a vanguard of devs ("AI champions", as they're called) over the past 2 years to ensure the decision to pivot to Slop-Driven Development comes off as relatively bottom-up.

[–] Snort_Owl@hexbear.net 5 points 2 days ago* (last edited 2 days ago)

There will always be class traitors gunning to fuck us all with the vain hope they can leave us all behind. I hate it all because I live and breathe computer nerd shit and have done my entire life, I really care about my craft and these absolute assholes just continue to shit all over it time and time again. I don’t do it for the business I do it cos I like making good systems.

[–] Enjoyer_of_Games@hexbear.net 25 points 2 days ago (3 children)

In theory; yes, under capitalism; no.

I think we need to lean on Al to speed up PRs

Same old story. Good, Fast, Cheap: which two are gonna get picked?

[–] fox@hexbear.net 14 points 2 days ago

With LLMs in the loop you can drop cheap. You can have it good or you can have it fast, and the more you choose fast, the worse good will become.

[–] Abracadaniel@hexbear.net 11 points 2 days ago

Cheap and good please.

[–] doubledealer@hexbear.net 12 points 2 days ago

Whenever you see anything like human-in-the-loop, read or hear that synonymous with fall-guy.

I don't know how to push back on this while being taken at all seriously. It has me considering that maybe I'm in the wrong for rejecting a tool that is considered useful by all but a few stick in the mud devs, and that those devs will never have a shot at a job again unless they pull their heads out of their asses and join our modern "AI"-driven world.

Right now you are arguing against money, greed. The cost is still being highly subsidized and at work it's basically impossible to argue against money and this shit literally rots peoples brains. It feels like the same kind of position as being COVID conscious coming into 2027 where some people are so damaged after repeat infections the concept can't even register and you seem crazy for wearing a mask as they cough in your face.

Anytime I have to use Super Intelligence shit I document from prompt-to-flawed output, documenting any new vulnerabilities and risks, cost, etc. In theory any middle manager pre COVID/AI brain rot would be able to use this to stab their peers in the back when shit hits the fan and somebody hopefully somewhere in the C-Suite realizes they were ripped off. When the actual cost of running a prompt is passed to the business consumer they should balk at what they get, it should be criminal. I don't think many executives will actually take any accountability, even admitting that they were duped.

[–] JoeByeThen@hexbear.net 18 points 2 days ago* (last edited 2 days ago) (1 children)

Yes. You get an abliterated model and an open source coding agent and you say, "Agent, how would you cause as much damage to the military industrial complex as possible while making sure to cover your tracks?" And then you make sure nothing tracks back to you because you don't use any services connected to you including your own internet. Piece of cake, in Minecraft.

[–] thefunkycomitatus@hexbear.net 15 points 2 days ago (1 children)

"Do a revolution for me, make no mistakes" and do it behind 7 proxies.

[–] DogThatWentGorp@hexbear.net 10 points 2 days ago (1 children)

Code you wrote yourself and make less dogass in the first place needs to be changed less after reviewing it no? And doesn't manually reviewing code help you understand what you're working on and how to write better in general?

I got a hunch this is me not understanding the industry, but I feel like LLMs only make sense in a world where productivity is measured based on code output.

Need more mindless fluff? Great news. Need to spend more time writing fluff and you wish something else could do review? Does your team not write high volumes of code? Train the LLM on a high volume dataset.

Like iunno. Maybe that's part of it. Just a broken industry practice getting more brokener.

Also what another user said with the tokens. Once the bubble pops and/or the financial crunch on LLM companies start the cost is going to jump to the point where none of this won't matter. (I hope anyways)

[–] AppetiteOfExcess@hexbear.net 6 points 2 days ago (1 children)

I got a hunch this is me not understanding the industry, but I feel like LLMs only make sense in a world where productivity is measured based on code output.

It's being pushed moreso to make more features than to make more lines of code. The latter implies the former, of course. The upper management types love going on about releasing features at tHe SpEeD oF aI.

[–] DogThatWentGorp@hexbear.net 5 points 2 days ago

To think when I went to school they emphasized so much about iteration and making a solid base to build off of and now they're saying shit like "the speed of AI" and letting it make god only knows what kind of spaghetti.

Like in your experience having to work on a team using it, do the the LLMs have a concept of making sure the code is expandable later down the line? Or even just making sure there aren't super awkward coupling snaffus? I feel like even just casually programming I've been seeing more instances of the most bizarre hierarchy and coupling choices but that could also just be me learning to be more mindful IG.

[–] delfick@lemmygrad.ml 6 points 2 days ago* (last edited 2 days ago)

The people who think these tools work only do so because they don't seems to know what software is or how it's made.

This idea of "human in the loop" needs to go away (as in the problem is using an LLM to make code. That cannot be compensated for, and people need to go back to taking this job seriously). It doesn't work and it only leads to ever increasingly complicated process fever dreams to try and compensate with the dissonance in their head that they so strongly believe the hype that they refuse to accept they're being lied to by the same kinds of people that made social media addictive.

also, these tools are used by business people who have even less understanding of software to give more work to less people. And the way people respond to that with "I can't move that fast, so my new aim is to move faster" is so incredibly self defeating. It's so unserious.

My eyes roll out of head whenever these kinds of people realise that the way to make the LLMs reliable enough (though often their concept of enough is broken and what they're producing is not good) is by doing software engineering practises with an unrealistic level of discipline and somehow still sell this as them doing less work

[–] CHOPSTEEQ@lemmy.ml 12 points 2 days ago (2 children)

We “invested” in some hardware to experiment with LLMs before agents took off, so we’re thankfully running open models on infra we own. That removes a lot of the moral problems imo

As a former 100% “not using that ai shit” guy, I still can’t give up reviewing every single line of code in the stuff I’m responsible for. Add enforcing my opinions on it, it probably would’ve been faster for me to just do it.

But what I have found immensely useful is sicing it on code I absolutely do not give a single fuck about. Vscode extension doesn’t work how I want? Clone it, tell qwen to fix it, go back to doing valuable work. If it fixes the extension, great, if not, oh well. And if it’s slop, it’s not my problem.

[–] someone@hexbear.net 10 points 2 days ago (11 children)

That removes a lot of the moral problems imo

Only in usage, not in the creation of the LLM in the first place.

[–] Biddles@hexbear.net 8 points 2 days ago (1 children)

Only in usage,

Not even in usage, the electricity necessary to run the model for any given output is probably just as high as it would be in a data center

load more comments (1 replies)
load more comments (10 replies)
[–] AppetiteOfExcess@hexbear.net 4 points 2 days ago

But what I have found immensely useful is sicing it on code I absolutely do not give a single fuck about.

That's increasingly becoming all of my code at work lol. I used to care about quality in a "don't shit where you eat" kind of way, but if C-suite wants slop, they'll get slop.

[–] chgxvjh@hexbear.net 5 points 2 days ago

Maybe but I think that leads to getting fired for not producing enough output.

[–] Big@hexbear.net 7 points 2 days ago

Does roleplaying with Mpreg Fred Flintstone count?

[–] pcalau12i@lemmygrad.ml 2 points 1 day ago

You need good testing suites, especially unit testing which people often forgo. If you have good testing then it's no issue.

[–] Abracadaniel@hexbear.net 5 points 2 days ago

I think so, but I think we're all actively trying to figure what that looks like.

[–] aanes_appreciator@hexbear.net 6 points 2 days ago

Possible? Yes.

Do many devs even bother? Lol.

load more comments
view more: next ›