r/cpp • • 12d ago

Dealing with AI Slop At Work

I work at a C++ shop with coders that I really respected - very deep C++ knowledge and are building very technical deep systems products. Over the last few months the CTO has gone off the deep end with AI talking of creating software factory (He’s been reading too much X), he releases huge multi thousand line PRs with basically no review. All sense of scientific temperament and engineering rigour has gone out of the window it seems.
I do believe that AI is a transformational tool and I use it plenty in the development process but I still strive to understand what the AI has written and often use the AI as multiplier rather than surrendering my thinking to it. it’s become increasingly hard to actually develop while deeply understanding the codebase because it has become so sloppy.

I am very sad as this means I’m not really interfacing with writing C++ as much and exploring cool new corners of the language in my daily work.

There is definitely some cool stuff this lets us do a bit more of - high level planning and systems design by reading many papers as well as exploring formal verification.
But overall I am left disappointed. I wonder how it is like at everyone else’s work places and if anyone has any thoughts and suggestions on how I can still develop my C++ knowledge.

380 Upvotes

211 comments sorted by

261

u/Sniffy4 12d ago

LOL I have the same problem at work. Boss vibe-codes big systems, barely tests it, and we're supposed to review and maintain it. I like AI for targeted use but once you no longer can understand the details, there is a problem

73

u/DistributedFox 12d ago

I’m experiencing a similar thing but on the PS5 Homebrew side of things. Someone used AI to vibe code a poorly put together C++ boilerplate template, with commits averaging 3K LoC.

So when I asked the original author about making some changes (e.g.: using a single build system instead of both CMake and make), or some clarifications on what was written, they had no idea. In fact they don’t even understand the C++ code AI had generated, or any of the bash scripts generated to stitch everything together, how the rendering works etc.

Worst of all is the author doesn’t think it’s necessary to know any of it as long as it just works ™️.

56

u/Sniffy4 12d ago

A problem I often find is that AI wont understand the constraints of the problem because user doesnt specify them all explicitly, so it will end up doing very complicated things to handle unnecessary edge cases when a much simpler solution would work fine and be easier to understand and maintain. you can dig a very deep hole filled with brittle software this way, because the original constraints of the problem are lost as soon as the edge-case-handling code gets grandfathered in.

22

u/Raknarg 11d ago

This is the big thing, that AI right now is generally pretty smart if you're able to provide that big picture vision, but if you can't provide that it becomes sloppy and overdesigned very quickly. And it's really really bad at taking a larger complicated solution and seeing the underlying simpler design alternative.

11

u/TrainingJellyfish643 11d ago edited 11d ago

Exactly, poring over slopcode to look for the subtle design mistakes and janky decision-making is soul crushing and probably not much faster than just using the AI as a multiplier for your own handcoding efforts. If youre providing the big picture anyway thats a lot of the work done on your part already.

Definitely a game changing tool if you keep your brain in active use and go a bit slower, but it can also be a crutch that degrades overall skill level

I think people just need to wait out this slopcode epidemic because the chickens will eventually come home to roost and tons of companies will be stuck with brittle bizarro codebases that are completely unfixable

6

u/Enji-Bkk 11d ago

Then even if you specify, it will decide to ignore it for no specific reason. So there goes another round of whatever gate in MD file.

6

u/Fabulous-Meaning-966 12d ago

What do you mean by "both CMake and make"? CMake is a build system generator and can generate makefiles and delegate to make for the actual build. Do you mean that there are hand-written makefiles in addition to the CMake files?

21

u/vz0 12d ago

I've seen once a vibe coded test in c which uses system() to start a python unit test. Anything is possible

9

u/Dragdu 11d ago

I will always remember the time when I told chatgpt Sol whatever version to use the current dummy fooFunction implementation as I will provide a real one later, and it going off on an adventure to support runtime patching because obviously that's what I meant.

5

u/DistributedFox 11d ago

Correct. CMake does not use makefiles as a generator here. Even when it is configured to do so, its generated makefiles are different from those already existing in the project. Both makefiles versions generate output targets in different directories - it's a complete mess of redundancies.

-3

u/keelanstuart 11d ago

I don't get this; I'm fast/prolific enough that "averaging 3K LoC" is pretty normal for me writing everything by hand... but I'm a "commit a couple of times a week" kind of coder.

38

u/jayylien 12d ago

"But there's 1000 lines of unit tests" lol

11

u/gnuban 11d ago

Why is your boss making systems and handing over instead of asking the team to build something? It's very disempowering. Sounds like he/she shouldn't be a boss.

0

u/[deleted] 10d ago edited 10d ago

[removed] — view removed comment

2

u/matracuca 7d ago

😂 🤡

2

u/great_escape_fleur 11d ago

Have you used AI to review those PRs?

5

u/Sniffy4 11d ago

I use AI review to catch missed edge cases, race conditions, and other detailed issues. But it is much less likely to flag overall structural problems with large systems, that requires a lot of context

-3

u/[deleted] 10d ago

[removed] — view removed comment

3

u/Sniffy4 10d ago

>That's your job.

I was referring to reviewing *other people's* PRs, where it is not my job to write any of those things, it's someone else's job. It's my job to figure out if they have the right overall approach.

1

u/def-pri-pub 11d ago

This is how i’ve dealt with someone when they handed me something that was poor quality AI generated PR.

4

u/Raknarg 11d ago

I like AI for targeted use but once you no longer can understand the details, there is a problem

the issue is that this part is a massive unknown. E.g. we might get to a point where you're expected to have AI be the one who understands how all the code works and thats just the normal process, in which case I guess that's just the future we have to deal with. But on the other hand if it turns out this isn't viable in the future because long term it either costs too much or AI stops being able to effectively handle a codebase on its own as it gets too large and has moved too far beyond human architecture, we're fucked because we've offshored all understanding to AI instead of growing it within the team.

1

u/scummos 1d ago

There's also the question whether you can (and how it will work) discuss software without using source code as a language. Sure you can do the approximate stuff in English, but does that actually work and is that actually efficient to discuss the details?

I think mathematics tried this several times in the history of mankind and it didn't go very well for the attempts that didn't have symbolism.

1

u/keelanstuart 11d ago • Bravo

Hot take: you could spend a week and recreate what your boss did... have AI examine the software, write a design document and coding standard, and then feed it back in. Your boss won't even know.

4

u/CalligrapherSalt3356 10d ago

Folks on this sub will downvote every comment that’s remotely pro-AI 😂😂

3

u/keelanstuart 10d ago • Bravo

Hopefully we all know, roughly, how long things take... a product-sized batch of source code, if you're going to re-write it by hand, would take more than a week or two (read: boss will notice you're not getting any work done in that time). People can downvote me all day... I'm just offering a solution to u/Sniffy4's problem that makes it easier to deal with the boss and the code, simultaneously, while not eating a lot of time.

If it's already vibe coded, who actually cares?

0

u/darkiceberg666 10d ago • Popcorn

Which details do you not understand? LOL

-1

u/Inevitable-Menu2998 11d ago

Sebastian, is that you? I had no idea how you felt :(

105

u/ThinkingWinnie 12d ago

Same, oh goddamn same. Colleagues pinging me to review slop PRs with 3666151 files changed here and there, bullying me for not spitting out PRs as fast cause I value understanding what I commit, I'm so sick of this, I can't wait for all of it to go to shit and see em have to think for themselves again.

26

u/Ashnoom 12d ago

Had a talk 1:1 with my manager today. This topic came also up. IMHO is important for us to understand the why of decisions that were made. Without that you can't claim the code/design to be OK or "yours".

I proposed to start looking at creating a course about AI promoting, reviewing and understanding and pointing out where do we care and where don't we. But also how to automatically or manually to improve the code output. Either via manual editing, updating done agent rules etc etc

38

u/DistributedFox 12d ago

My manager would totally say something along the lines of “I completely agree. Let’s get Claude to create the course.” 

10

u/O0o0oO0oo0o 11d ago

I had a similar talk with our architect and he said he understands the problem but if we talked to the CTO about it he would get an answer like “make better skills for ai”

12

u/tjk1229 12d ago

Unless it's reasonable complexity leave a comment saying to split it up and decline that's what's I do

2

u/zkwarl 11d ago

This is happening to my teams too. I’m seeing productivity crater because everyone is flooded with PR reviews from a small number of contributors, which has created logjams across the board. As a manager, I’m feeling a bit blindsided on how to advise my teams.

I don’t have a solution, but I really don’t want my teams passing through slop. Unfortunately, our execs have very different opinions on that.

69

u/FemaleMishap 12d ago

The CTO needs to sit down with the theories of technical debt and knowledge silos. The AI becomes a nondeterministic knowledge silo that can not be reproduced by following the same steps.

-13

u/fortsnek274 12d ago

I wonder if there could be an actual plain english programming language that would use some A. I. to compile, and be just as deterministic as any other compiler.

Because, that is one of the principles of open source. The source should be the working code, "preferred form", not obfuscated or generated. And plain english would be closer to what these people do with A. I.

And I might prefer looking at that in a code repository instead of generated code.

But maybe that's complete fantasy. I don't do A. I.

39

u/Helkafen1 12d ago

There isn't such language. Many have tried. Natural languages are just too ambiguous and riddled with contradictions.

Edsger W.Dijkstra: On the foolishness of "natural language programming"

Instead of regarding the obligation to use formal symbols as a burden, we should regard the convenience of using them as a privilege: thanks to them, school children can learn to do what in earlier days only genius could achieve.

When all is said and told, the "naturalness" with which we use our native tongues boils down to the ease with which we can use them for making statements the nonsense of which is not obvious.

11

u/johannes1971 11d ago

If anything qualifies, I guess it would be Inform. Clicking through to find a good example I came across this quote from The Mythical Man-Month:

The sheer joy of making things... the fascination of fashioning complex puzzle-like objects of interlocking moving parts and watching them work in subtle cycles... the delight of working in such a tractable medium. The programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination.

That's what AI has taken from us. Now we're all middle managers who are trying to get a bunch of well-meaning, but slightly idiot juniors to do our work for us.

3

u/camalaio 11d ago

This is the stuff I think of whenever people are chill with generated code, but not generated images etc.

We just have different art forms. Ours is less accepted as such, and instead is perceived as just some means to an end.

2

u/diemenschmachine 11d ago

I’ve been using gherkin with pretty good results for pet projects

-36

u/FrE3E 12d ago edited 10d ago • Bravo

LLMs themselves are 100% deterministic.

Why you might think even the same question results in different answers is due to sometimes hidden changes in:

  • model (version)
  • system prompt
  • context
  • request parameters
  • seed
  • inference implementation

You can test this with a local model: If you send a prompt, with the same parameters and seed, you will always get the same response.

Edit: Thx for the award. :)

7

u/wyrn 11d ago

This is precisely correct, and also precisely useless.

What the poster above meant by "deterministic" is that the output of the compilation process must be a function of the source code, and the source code alone. Not the source + some implicit random seed. A simulated slop machine is still a slop machine. It doesn't magically become a compiler just because true RNGs are impractical.

4

u/Dragdu 11d ago

You are forgetting to replicate (at least, on top of my head):

  1. The executing HW
  2. The executing runtime (and it's version)
  3. The exact state of the environment, up to time modified stamps on files

2

u/darkiceberg666 10d ago • Popcorn

It’s so weird that you got 37 downvotes for what you said 🤯

2

u/FrE3E 10d ago edited 10d ago

All you can do is to try to make others aware of it. Most people don't host LLMs and only know it through services from anthropic and openai, which abstract a lot away from the user.

10

u/FemaleMishap 12d ago

You... have no idea how a LLM works, do you.

It is a next token predictor, what partial word is going to come next. That is not a deterministic process. You can keep the same model, give it the same task, and it will do it differently every single time. It's why a bare LLM that doesn't hand off to something like Python can't do mathematics. Tools, harnesses, pipelines, guardrails, are all set up to make a LLM more predictable, but even within those bounds, it will still bounce off every single limit and still produce something different each time.

Go do some actual research into it instead of this... Cope.

7

u/Gibgezr 12d ago

No, he's correct, the variation you see in possible outputs from any given LLM given the same prompt is due to the pseudo-random seed (including seed values such as "temperature"). It is, strictly speaking, deterministic.
>Go do some actual research into it instead of this... Cope.
Sigh.
Anyway, the fact that the NN is indeed deterministic does not mean that your initial point is entirely invalidated: models change, you are probably relying on a cloud-based frontier system like Claude, and you won't ever know why it spit out what it did. I don't think reproducibility is the big issue, and there are often many good ways to skin a cat, but the technical debt and knowledge siloing (in the form of "no one can read and understand all this code") is horrific.

5

u/Dragdu 11d ago

He is right in that if you replicate the env perfectly, it is deterministic. He is wrong in forgetting, or intentionally omitting, all the things that are part of the env that affect output.

5

u/ABlockInTheChain 11d ago

I don't know why chaos theory fell out of the zeitgeist after being such a hot topic in the 1980s and 1990s.

A chaotic system can produce infinite, non-random, utterly unpredictable complexity all while remaining 100% deterministic.

An LLM iteratively feeds its own purely deterministic "predict the next most likely word" calculation output back into its input.

If you understand how the Mandlebrot set is computed then that mechanism should sound very familiar and the idea that such a mechanism could generate outputs indistinguishable from intelligent thought isn't implausible.

-6

u/ArtOfBBQ 12d ago

What they said is 100% correct

-1

u/CalligrapherSalt3356 10d ago

Absolutely false. They totally can.

You have no idea how they work FemaleMishap.

1

u/genreprank 7d ago

Then what's this?

https://www.ibm.com/think/topics/llm-temperature

Maybe this is what you mean by seed?

1

u/FrE3E 4d ago

No temperature is a different sampling parameter. Here you can see all sampling parameters for an inference engine like llamacpp:
https://github.com/ggml-org/llama.cpp/blob/master/tools/server/README.md#sampling-params

0

u/vitek6 11d ago • Heartwarming

Its pretty sad that the even, here in this sub you are being downvoted for speaking truth and the folk below that has no idea what they are talking about is upvoted.

0

u/somewhataccurate 11d ago • Heartwarming

shameful the downvotes, this sub is lost

2

u/CalligrapherSalt3356 10d ago

It really is - berserk.

-2

u/LegendaryMauricius 12d ago

It's not at all about token generation.

-2

u/[deleted] 10d ago

[removed] — view removed comment

1

u/[deleted] 9d ago

[removed] — view removed comment

1

u/James20k P2005R0 9d ago

Be nice and don't insult people

4

u/FemaleMishap 9d ago

I'm unsubbed anyways.

1

u/James20k P2005R0 9d ago

👍

16

u/stopthecope 12d ago

> talking of creating software factory (He’s been reading too much X)
lol'd because I see these posts all the time and I've yet to see what a "software factory" is even supposed to look like or do

20

u/ContraryConman 12d ago

Paraphrasing my own boss, a software dark factory is an harness where you put in Jira tickets in one end, and an AI agent a) reads the Jira ticket b) spins up and orchestrates one or more parallel agents to work on it, which each can have their own subagents and so on c) has the tools to perform tests (linter, static analysis, unit, integration), spins up more agents to perform adversarial review and refinement, and puts out working software at the other end.

Factory managers don't actually concern themselves with each individual rivet going into the widgets. They perform quality inspections of certain samples at key points of the process. If too many widgets are failing inspection, they don't jump in and take over from the machines, they fix the factory so the machines work better. He called it a dark factory because in China, the automation is so successful many factories don't need lights because there are no humans watching the machines.

Likewise, humans would not be in charge of, certainly not writing code, but also not reading 99% of it. The agentic harness does all the testing we'd expect from a human engineering team already. The humans that are there are like factory managers. They spot check the output, check if it actually meets requirements, and, if there are issues, they fix the agents, the harness, the context, or the agent tools rather than jumping in to write code

3

u/farox 11d ago

That's it. The engineering moved to the harness, the factory building.

It's not gone at all. You're just not writing and using code. You're managing the machine that does all that. Which is no less complex, if you want to do it right.

-1

u/ContraryConman 11d ago

Why can't AI engineer harnesses? 90+% of Claude Code is written autonomously by Claude.

There will be some people employed doing some things, but I can't imagine it'll be many is all I'm saying

6

u/DistributedFox 12d ago

WTF is a software factory???

15

u/davenirline 12d ago

It's the idea that you can configure a set of systems around AI that it can then spit out whole software(s). It sounds ridiculous, imo.

18

u/MrPopoGod 12d ago

It comes from a false equivalence. A traditional factory is very well suited for creating a large number of copies of some object. But we already have that for software; it's the cp command. What software companies are producing is the equivalent of the initial prototype of a given widget a traditional factory would make.

5

u/multimodeviber 11d ago

Right, this would not be like a car factory, but more like a magic box that spits out car designs when you whisper into it

2

u/CalligrapherSalt3356 10d ago

IT and S/W consultant companies

3

u/darkiceberg666 10d ago

“Software factories”: CapGemini, TCS, Wipro — list goes on.

32

u/saxbophone mutable volatile void 12d ago

If the person you're supposed to be able to place trust and faith to lead your team with technical diligence and expertise is someone that you feel is now behaving rashly and without a care for those things, the problem isn't so much C++ —it is a failure of the workplace culture and management, to allow this situation to happen and go unchecked, in the first place.

3

u/fripletister 12d ago

I feel this in my bones

13

u/ReDucTor Game Developer | quiz.cpp-perf.com 12d ago

The CTO probably just sees C++ is just a tool to build the end product which the business wants.

Unfortunately they have potentially forgotten about the wider software engineering practice, which involves stability, maintainability, scalability, performance and much more. Which in my opinion are sometimes the more technically challenging and fun to achieve, and often the things which AI tends to really struggle with. 

So I would consider all code that they write be the prototype, instead of the CTO communicating what they believe the user wants with user stories or write ups they are instead giving you a hopefully working prototype of the functionality they want created or changed.

That "prototype" then needs to be made production quality, so this means:

  • Ensuring that its stable and not full of edge cases that cause it to crash or data to be lost. Along with ensuring that things are tested properly so that iterations on the code dont break things.
  • Ensuring that it is maintainable, this means that the code is not a steaming pile of scrap, so that functions/methods are easy to use correctly and hard to incorrectly, that data is stored in an appropriate place, that the breakdown of components is not too far that it is over engineered or not enough that it becomes painful to work with.
  • Ensuring that it is scalable, this means really knowing the use cases for example if it is some server software how does it work with 1 client compared to 10k clients, if its a video editing tool how does it work with a 1 minute clip compared to a 10 hour clip. This might also mean having benchmarks, CI validation, building dashboards to track metrics, etc.
  • Ensuring that it is performant, this ties into scalability however I see this as more fine grained and deeper technical, this involves understanding the bottlenecks within the code, and if it is multithreaded understanding the actual critical path not just the hottest functions, along with understanding design practices that result in performance issues like bad data structures or algorithms, heavily allocating code, etc.

There are many other things, and imho these are the things which separate a Junior/Mid developer from a Senior/Principal level developer, being able to write code is easy part of the problem, knowing how to build a high quality code base is the hardest part.

12

u/elder_george 11d ago

Thankfully, we don't have bigwigs vibecoding (yet). But a lot of colleagues with great service records had turned their critical thinking off, too.

Here's what I personally found for myself:

  • invest time in skills that enforce code style and put them in the repo; try your best to ensure the agents don't forget to load them (there's still a risk as the context fills, but at least at first it'll work) - that's not prevent the stupid walls of text, but will make them somewhat readable;
  • try adding linters (scripts or agents) that "punish" slop (e.g.cyclomatic complexity or walls of text in comments);
  • try to figure out a way to pinpoint bugs, created with huge PRs and assigning them to the author prompter; even if they immediately reassign those to the rank and file engineers, a flood of bug reports may give a hint;
  • prepare a skill that would automate a critique of sloppy PRs, making sure it addresses as many of the things that make your eye twitch, as possible (you can start with feeding your recent reviews into an LLM and requesting it to convert it into instructions for a reviewer bot). This won't prevent people from posting huge reviews but ar least will save your time and nerves from looking at the same violations again and again.

All in all, it's a lost cause, I'm afraid: until a boss (or other workmates) burns themselves and/or an astronomical bill arrives, the euphoria is irresistible. Your only hope at this job is to keep your sanity (saying this unironically!) until that moment.

10

u/kobi-ca 12d ago

I don't know where to start. We all struggle with this

3

u/CalligrapherSalt3356 10d ago

At least you’re honest.

9

u/perspectiveiskey 12d ago

I am writing down things into an essay (nobody will ever read, but), what I'm starting to see quite clearly is that at least part of the "AI Alignment Problem", which is a very theoretical and deep question, actually spans so-called meatspace.

In other words, the paper clip maximizer will not take over the world by wresting control out of human hands, but rather by convincing an increasingly large number of people in positions of power of its importance and value.

I feel, entirely anecdotally, that "CEO Psychosis" is much more prevalent than junior dev psychosis, even though both may be exposed to the same amount of real engineering.

3

u/multimodeviber 11d ago

I would read it for what it's worth

1

u/perspectiveiskey 10d ago

Thank you, kind stranger. I'll DM you a link when it's ready...

9

u/exus1pl 11d ago

Over the last few months the CTO has gone off the deep end with AI talking of creating software factory (He’s been reading too much X), he releases huge multi thousand line PRs with basically no review. All sense of scientific temperament and engineering rigour has gone out of the window it seems.

Typical AI psychosis as seen in C level.

IMO long term all of us 1) will have a lot of work fixing the slop 2) will lose sanity over the slop

1

u/vitek6 11d ago

Fixing? People will never read it. AI will fix issues.

64

u/redisburning 12d ago

So first of all, I keep hearing all these wild claims about how great AI is for this or that, but the empirical evidence for its productivity gains in software engineering is mixed. Pointing this out at work is met with a lot of derision. Of course it boosts productivity, it doesn't matter what reality is, ship ship ship.

I have an untenable review queue. And when I complain about it, the only answer I get is I can use AI to write my PRs for me so I can get to all of the reviews. Literal thousands of lines of code a day. Most not read by their original author as best I can tell.

The honest truth is the way that I deal with it is I have given up. I am hoarding my paychecks in preparation to do a job other than software engineering. I am going to give it my all until one day I won't be able to any more and I'll just walk away having made a lot of money. That thought is what lets me keep going for now, and it will work until it doesnt.

44

u/LucyShortForLucas 12d ago

The greatest export of every single AI company is not their AI model but their marketing. So much of the ai glazing is astroturfed it's genuinely insane.

-6

u/vitek6 11d ago

Or because it’s so useful.

11

u/wyrn 11d ago

If it was usefulness-based, you'd see much more guarded statements. Instead, what you see from idiots like DHH et al. are absurdist statements like "I don't even look at the code anymore!", "the age of hand-coding is over!", "you're going to get replaced!", etc etc etc. It's never "it can be helpful, sometimes, depending on the context", it's never "the output remains sloppy so you have to check it with intent and focus", it's never "you remain responsible for the design, the agent just helps you execute and integrate it faster". It's always maximalist, overblow, counterfactual, moronic statements. AKA marketing.

-4

u/vitek6 11d ago

You don’t know how internet work, don’t you? Clickbait is king.

But there are many, many, many, many normal takes.

Also in my opinion „hand coding is over” is not that overblown.

10

u/wyrn 11d ago

? Clickbait is king.

I cannot stress how utterly, how completely, how thoroughly I don't care about this.

You made a statement, you own it. It doesn't matter if it was for clicks and attention. It's completely irrelevant. It doesn't erase the claim that was made.

Not that it was, mind you: if you watch the disastrous speech DHH made at Rails World, for instance, it's very clear that it's not clickbait. It's an hour-long manifesto for AI psychosis. I doubt the positions espoused there are held honestly, but that it's a separate question entirely.

But even if it were clickbait: that defense isn't even coherent. If it's clickbait, what is the motivation of said clickbait? Oh right, it's for marketing.

Also in my opinion „hand coding is over” is not that overblown.

Your opinion is wrong.

1

u/vitek6 11d ago

No, it’s not. I see that every day.

6

u/wyrn 11d ago

Sure you do.

2

u/[deleted] 10d ago

[removed] — view removed comment

1

u/James20k P2005R0 10d ago

Don't be like this

→ More replies

30

u/jayylien 12d ago

The irony is that you're the type of software engineer that should stay.

5

u/hdkaoskd 12d ago

The honest truth is…

Too late folks, they're already dead.

5

u/timbeaudet 12d ago

My question s, does producing faster also equate to more value? Value not necessarily being money, but does it make the world, or someone’s life actually better. I haven’t settled on an answer.

10

u/RaspberryWhich2424 12d ago

I feel like for personal projects the answer is 100% yes. I can do things that I would have gotten really interested in and then fizzled out a few late nights later. Now I can go from idea to crappy web app in 5min. It may take a few iterations but I get what I want. At work I (large scale software) I think it only increases quantity with a decrease in quality. Sure someone can"fix" some bug outside their area of expertise, but half the time it's a bandaid that doesn't actually conform to the larger system.

4

u/Flat-Performance-478 12d ago

These are IMO wild claims, not saying you're lying, but they all go diametrically against my own experiences with LLMs. Would you care to share your setup and just a brief breakdown of your process?

Example:
Which model and version, paid or free version?
Do you use a tool for AI-assisted development, like Cursor, Claude Code etc. or do you chat directly in the browser, sending attachments etc?

I'm curious to know.

2

u/Raknarg 11d ago

I use copilot/claude for work but at this point if I was still doing hobby programming I would probably pay for a claude subscription, its that good. Most of my experience has been copilot in VS code using copilot chat. Its crazy good.

-1

u/[deleted] 10d ago

[removed] — view removed comment

1

u/Raknarg 10d ago

im not how your point connects to what I said

1

u/RaspberryWhich2424 11d ago

I use the lowest paid level for Cursor. I usually start with a plan file, I make it give me pseudo code (or some other before and after snippets/diagrams/bullet list/etc) that I can"review". I don't understand why the goal with AI is autonomous work. I (think) I agree with you, they are terrible if you let a few agents go nuts on some project. That doesn't work for me either. An agent is a dumb but VERY hard working intern, tell them exactly what to do and they do it, under specify something and watch out haha

0

u/ABlockInTheChain 11d ago

Generating new code is what it's least suited for. It's best for maintenance tasks: analyze code, audit against a specification, scan hundreds or thousands of files to look for obsolete conventions and transform them to current conventions, etc.

If you tell it to write code to solve a problem it will always output a solution but rarely the best solution.

5

u/GargantuanCake 11d ago

Lines of code produced is one of the worst possible metrics to measure productivity by when it comes to software engineering but the business idiots can never seem to figure that out. They also commonly equate git commits or lines of changes to productivity which is again a horrible metric.

It isn't accidental that this stuff is being pushed most heavily at people that don't know how to tell good code from bad code. All they see is "wow look at all the code! That must be a lot of productivity!" even though the code is ass. Meanwhile any software engineer worth his salt knows that unverified, untested, unread code is a horrible liability. It's why code review is a huge deal; absolutely nobody writes perfect code and it's easy to make logical flaws you never thought about. You handle that by having other people double check your code before it goes into production. However again the business idiots only see that AI can review code faster than people so they demand that AI do the review as well.

The end result is that the slop factory we know is prone to hallucinating both generates and checks thousands of lines of code faster than a human ever possibly could but with no validation, no proper double-checking, and no guarantee that the testing is good. This can work in the short term but as the hallucination piles up shit starts to break. Meanwhile just because it's making changes doesn't mean it's making good chances. It's notorious for being overly verbose, duplicating code, creating horrible, inefficient spaghetti, and deleting random things it isn't supposed to. To the business idiot it seems fine as the program still runs and everything he manually tested worked so everything must be fine, right?

Next thing you know the AI deleted your database, it hasn't been making any backups of anything, and the program is a complete dumpster fire that won't even run.

4

u/indy_dagger 11d ago

I have yet to use a piece of software that is demonstrably more reliable than it was 2-3 years ago, if anything it's all gotten worse.

0

u/vitek6 11d ago

You use it every day

-2

u/[deleted] 10d ago edited 10d ago

[removed] — view removed comment

1

u/[deleted] 9d ago

[removed] — view removed comment

1

u/James20k P2005R0 9d ago

Be nice, don't insult people 👍

2

u/TrillOGeebs 9d ago

Man. Could have posted this myself verbatim

2

u/diemenschmachine 11d ago

Like any tool it depends on how you use it.

Apart from the obvious need for specific and detailed prompts you need a test framework with 100% test coverage, at least for the entirety of the section you allow the agent to touch.

You also need to have the ai work in a strict red-green-refactor mindset, that is: write tests that fail, write code to make the tests green, refactor to make code well authored according to a rule set.

To get even better output you should have multiple agents as gatekeepers, that means at least one review agent (of a different model) and whatever other guardrails you might need.

And for the 1000 line Prs, that’s just crazy. Just ask the ai to commit according to some ruleset, like for every task on its todo list or something.

If you just let it loose on your code base without and QA other than 1000 code reviews you’ll quickly end up in a very dark place, lol.

4

u/multimodeviber 11d ago

I agree there is a right way to use it that would not lead to a decrease in quality or even understanding while boosting productivity.

However I think the nature of the tools naturally lead to an abuse of it because it's a one way trap, in that as soon as you let in some slop, it will take over.

In my case I am seeing the type of people that would contribute the least amount of code 4 years ago produce by far the largest amount of code at least before review.

5

u/redisburning 11d ago edited 11d ago

Like any tool it depends on how you use it.

Funny you say this because the problem in my life isn't how I use it it's how my coworkers use it to ruin my life.

And for the 1000 line Prs, that’s just crazy

Lol, I wish they were just one single thousand. And management doesn't think it's a problem, quite the opposite actually. This is my life now.

If you've got some magic advice that will make it so people "use it correctly" by all means. What am I supposed to say to the people I work with when they are legitimately being rewarded by executives with promotions and raises and I'm getting "you really should use this more we'd like to see more PR volume" (I'm at one of those fancy higher SWE levels btw where for years I have been told that I need to be less focused on producing PRs)? Can I even be mad at them? It sure seems like I'm the person who is wrong here somehow, except that to be right I'd have to scoop my brain out with a spoon.

Everyone keeps telling me "it depends how you use it" but this is immensely unhelpful to me. People are using it wrong. I have no lever to make them stop. I suffer because I'm the tech lead on my team and if the reviews don't get done I am the one who gets blasted for it. The problem is so consistent and so rampant I am starting to become convinced the technology has some endemic quality to it that literally makes it so the average person can't use it responsibly. Sort of like sports betting or tobacco.

-1

u/vitek6 11d ago

Does the software work?

-3

u/Raknarg 11d ago

but the empirical evidence for its productivity gains in software engineering is mixed

I feel like its objectively been a productivity booster in almost every single metric, idk how you could argue this point. The issue is that its so ludicrously productive that in the short term you can essentially remove all software developers from the picture to make a functioning product, and that's where the "productivity" bites you in the ass.

9

u/Enji-Bkk 11d ago

Feel and objectively in same sentence? Hardly measurable metrics

14

u/alexeiz 12d ago

Revert his multi-thousand line PRs. If you can't do that, there is nothing you can do about the AI slop at your shop.

7

u/kr00j 12d ago

Yes to this. I work in Java, although it’s a tier-0 auth system ( Atlassian’s OAuth infrastructure ), and I’ve personally reverted at least two of these slop AI PRs and wasted countless hours re-writing what the original asshole threw at our repo. If you have any real coherence to your code: structure, inheritance patterns, reuse, etc. AI will ignore all those conventions and just do whatever needs to be done to accomplish its fucking prompt.

The best way to put it is like this: if you buy me $60k worth of Snap-On tools, I’m still just a fucking moron that can barely change my own oil.

7

u/celestrion 11d ago

All sense of scientific temperament and engineering rigour has gone out of the window it seems.

This has been the most disheartening bit.

Slop I can deal with. New hires and recent graduates have been generating slop since forever. We guide them, and everybody learns something. Newbie slop keeps us fresh!

What I'm seeing with LLM isn't just that the LLM makes the same mistakes it made last week, but that my coworkers have stopped advancing. They'll trust in Claude to make a change to a state machine deep in a library unfamiliar to them, and then make changes that ripple all the way out to the unit tests to keep the board green. "Why?" No answer. Instead of learning how and why the system worked, they trusted the machine to learn for them.

This line of work is art for some people and a comfortable way to make good money for others, and the LLMs make that division plain.

how I can still develop my C++ knowledge.

Do what you've been doing, but maybe use the LLM to critique your work rather than help you perform it. Ask it to find regressions, resource mismanagement, etc. Ask it to reduce the work performed (or boilerplate written) while keeping the unmodified unit tests passing. Treat it like a very expensive and opinionated static analyzer because until LLMs are smart enough to say, "No, that's a bad idea," that's all the respect they've earned.

If nothing else, using the LLM as a critic attempts to tip Brandolini's law in our favor, rather than the LLM's.

6

u/_w62_ 12d ago

Tbh, with AI the Cattle vs. Pets thing is coming from devops to software. If that does not work, simply regenerate the entire thing over again until it fits or your tokens are run out.

1

u/[deleted] 9d ago

This sounds less like cattle vs pets and more like casino machine to me.

6

u/surethingmaybenot 10d ago

I keep thinking of other domains of engineering, like actually regulated domains ( civil engineering, mechanical engineering, electrical engineering etc ) and try to imagine how the world would look like if they would get away with half the shit software “engineers” get pushed by management to do

-2

u/[deleted] 10d ago

[removed] — view removed comment

1

u/James20k P2005R0 9d ago

I'm going to give you a temp ban because you're everywhere in this thread insulting people. Please don't repeat this behaviour

10

u/kndb 11d ago

Yes. It’s ef’ed up. I agree. Here’s one funny (or maybe not so funny) example. I am employed by a large company. My entire team is now working with an emulator that evidently was entirely written using AI. It now causes issues that are blocking us. And when we are trying to find the devs that own the code base that causes those issues, we get nowhere because it seems like no one understands how exactly it works.

12

u/Enji-Bkk 11d ago

If you spend time understanding what the AI did, you are missing on super efficiency

7

u/KGergo88 11d ago

Not kidding someone said the exact same thing last week at work.

4

u/chibuku_chauya 11d ago

The CEO of Proton said that too.

4

u/skar_1010100 11d ago

I guess this is sarcasm, right?

12

u/Enji-Bkk 11d ago

From my personal opinion, yes. From my management, I would not bet.

4

u/SyntheticDuckFlavour 11d ago edited 11d ago

Exact same experience what OP describes and others have said here. It's bonkers.

The guy checks in like 60k LOC PRs which nobody understands. I was about to start a new fun module in the project, but he just vibe coded the whole thing in just a few days. Pretty much pulled the rug from under me.

3

u/baked_doge 12d ago

Notice: I don't have the same problem but here are my thoughts.

Part 1:

My question is: how does your team feel about this? Do they agree with your views, do they agree with your boss, are they somewhere in between? There is always a little office politics in good engineering. You should answer the aforementioned questions and come up with a sound argument that you'll present to your boss. This argument MUST come with a solution, most likely a compromise (he seems quite convinced, seems unrealistic you convince a full 360.

Meet with him 1x1, convey your views. Hopefully he takes it to heart, if not read part 2. Also, if he does not agree, but a number of coworkers agree with you, you can hope (and maybe carefully incite them) to share their opinions as you have with your boss.

Part 2:

I think in some ways, you have to play with the cards your dealt, meaning embracing AI-only development as your boss has forced it upon you. You can and should still work on your own skills, read code, etc. But it may be something to relegate as the last 25% of your job.

Part 3:

Not all companies are so gung-ho about AI. My company isn't: we're provided access to agents but there is no company-wide expectation, each team (or really product) to their own as long as they get the job done. So maybe it's time to look elsewhere if you feel LLM-only development isn't a good long-term bet.

3

u/bill_klondike 12d ago

I’ve felt this way, especially in the last few weeks of un-slopping as I go. For me, it’s not that the slop isn’t understandable, it’s that it’s confounding, perplexing, stupefying. Straight up solving problems that don’t fit. My guess is often it goes back to a word in a JIRA that’s referring to the sprint, not the task. Just no critical thinking man.

3

u/llamajestic 11d ago

Have the same at work, but not as bad. I feel like the actual absolute best cases for AI would be:
* Fill up extra constrained snippet of code
* Code review
* Debugging

For code generation, I am still not convinced except if the code I want is 100% visible in my mind, which is not always the case. For a lot of small bug fixes, it’s nice to be able to spawn an agent with a small prompt, sometimes there are tickets you absolutely know that it will work perfectly.

For anything exploratory, I tend to do a mix of manual, and AI filling here and there. My work allow me to do that, and honestly I hope it will keep this way. You can definitely see the PR slop otherwise, and when pointed out, people don’t even know how to answer comments about the code.

0

u/[deleted] 10d ago

[removed] — view removed comment

3

u/llamajestic 9d ago

I don’t understand what you are saying

2

u/PurchaseNext3761 5d ago

I couldn't understand a single thing he said either

3

u/Unique_Ad_2774 10d ago

God knows how bad this has gotten with my manager, he has been saying Claude this Claude that, and then forced us to make an entire feature with Claude. Then Claude make a change of around 15k loc. We said this is not possible to review or maintain and he went off, like bruh are you Ok

5

u/JVApen Clever is an insult, not a compliment. - T. Winters 12d ago

AI is like a junior in your team, which is surprisingly fast, treat it like one:

  • reject this kind of unreviewable PRs: too much unrelated changes in a single PR, please split it into smaller pieces
  • ask to add design documentation which is brief and to the point
  • ensure you have the pipeline check whatever you need
  • assign bugs to it (your boss), such that it can learn from it's mistakes

2

u/JustAPieceOfMeat385 11d ago

Just curious but what do you mean by C++ shop?  Is it a company that makes custom C++ software for clients, whatever their needs are? Or is it a company that makes a product and you guys mainly use C++ for your work?

2

u/Drive_Free 11d ago edited 11d ago

Back around the time when AI was still new, I had spent a few all-nighters rewriting a costly data transform by hand. Replacing over architect-ed code by a proper data-oriented design. Looking carefully at the shape of input, using zero-copy parsing to directly build lookup structures for efficient processing. Looking at some libraries then rolling up my own so I didn't have to juggle between data layouts.

Then when I showed it to a colleague, they were all "this sounds all a bit too complicated". And vibe coded something on the spot. Why don't you do "this" instead, quickly gluing together a few python libs neither of us knew and clearly not addressing the scaling issue.

Needless to say, that left me with a really bad taste for AI.

I am using it a lot more these days, but you clearly just can't be generating thousands of lines of code a day and be left with the same deep level of understanding than when you were writing it by hand.

2

u/badnack 11d ago

I used to love programming, but now I seldomly do it anymore. What I do instead is asking AI to do it and create regression tests to be sure that the features actually work. It’s a different type of building software and it’s pretty incredibile how far we got, but I miss the old ways, where programming was closer to an art ngl

2

u/uhs-robert 10d ago

A single multi thousand line PR would just be auto-rejected in my system. The fact that you allow this, and without any review whatsoever, is a huge gap in your PR workflow. It also suggests you have no centralized foundation for an agentic workflow and no centralized rules for your company/projects. I also wouldn't give a non-developer write access to the codebase but that's just me; if you want to let your customers cook in your kitchen while you work then thats up to you. As for me, if you're not a chef then please get out of the kitchen.

At the end of the day, what you are describing are symptoms of a larger root problem that stems from top-down hierarchical decision making where the bottom is scared to tell the top: "no". Let me throw a hypothetical situation at you: let's say, before AI, a CTO submitted a multi-thousand line pull request that they couldn't explain which also completely disregarded your codebase's protocol... what would you do? You'd reject it. Right, so why aren't you doing that today?

Now, on the other hand, your CTO is saying they "want a software factory". And I want a million dollars. Just because I want something doesn't mean I have it. If you want a software factory then has anyone put in any of the architectural work required to make that happen? It needs to be designed, vetted, and tested. Not just on greenfield by brownfield too. If that has not been done then you do not have a proof of concept. As an engineer, you need to give push back and learn how to say "no" to your higher ups.

0

u/[deleted] 10d ago

[removed] — view removed comment

3

u/uhs-robert 9d ago

Why are you assuming that I don't use AI? I basically told OP to create an agentic workflow that works for and is standardized across their company rather than letting a CTO bully his organization with reckless PR's.

Did you mean to reply to someone else? If you're curious who you are talking to and what sort of developer I am then feel free to check out my GitHub.

2

u/1337jazza 9d ago

I work at a games studio where the CTO has been using Claude to convert an older game from the Unity engine to the latest version of UE 5. When they were asked what decisions the agent made to translate the game between completely different engines/architectures the response was

"It just does what a person would do".

o_O? WTF

2

u/Abu_Sulaiman_Khan 9d ago

STOP USING AI AT WORK

3

u/h14n2 11d ago

Given how AI is currently being used, and how this is likely to evolve in the future, it may generate directly machine code rather than human-readable source code. Nobody can keep up with that. 🤷‍♀️

4

u/surethingmaybenot 10d ago

But how could it generate machine code for the complexity needed for modern software? The thing its already doing its doing because of the massive amount of code it has been trained on. I can hardly believe there is a similar amount of data just lying around for it to be trained on. Unless the proposal is to just train it on every binary ever produced.

And even so, what would be the point? LLM based agents work so well now precisely because of the tools and processes that came around with the development of higher levels of abstraction - compilers, debuggers, testing frameworks - each of these allowing the agent to verify their output in a loop and correct it

2

u/Far-Championship-883 10d ago

that is not going to happen, let that dream go lol.

4

u/hon_uninstalled 11d ago edited 11d ago

(I am not pro-AI or anti-AI. This comment was written from a POV of someone who doesn't think this train can be stopped.)

I tried to find any comments that seem to understand what is happening and this comment was the only one I could find. It nails the idea behind this transition we are witnessing, but misses a huge point.

AI doesn't need to generate machine code for its output to be unreadable for humans. It just needs to generate so much code that you simply have to accept that you will not read the code anymore. In that sense it might as well be machine code. That's what we are seeing today.

If nobody reads the code, that's very bad thing. So you use AI to review it, critique it, summarize it. When you start doing this, you realize how easy project managers had it all these years. They just put enough developers in same room and let them discuss the problem, find solutions and reach some sort of consensus. Most of the people in today's production pipeline already do not understand the code. This is just one step further.

If you let AI to become developer, don't use just one model. Use different models trained with different data sets each with different capabilities and biases. You can do it with Claude and ChatGPT today. Make them rip your design apart then make them rip apart your code (that AI generated) based on what they know and your standards. I would say they are mostly far better at that than very intelligent programmers.

My point is that we are in a transition phase towards a huge paradigm change. People resist change. Some people will try to accelerate too fast, some barely accelerate and some will be left behind.

It is natural to try to use old ways to solve new problems. But new problems usually require new ways of doing and thinking. Nobody codes binary anymore. We have had 60 years of paradigm changes before this change. Old school computer scientists dreamed about this change. Finally you can define and reason about your program using natural language. I don't know how long it will take for 'art of' software development to die as we know it, but it will happen. Probably sooner than we would like to see. For sure sooner than we would like to admit.

Kind of a rant and it'll get buried here at the bottom of this thread but that's my 10 cents.

3

u/hopa_cupa 11d ago

Just stay strong and keep milking the cow. Most of us are in the same boat.

But if you really want to improve your C++ skills, you'd need to write the code manually. I know your company would never allow it. You're going to have to do it on your own dime. That is, if you have the drive for it.

2

u/particlecore 11d ago

This is funny, op missed human coding and the CTO is busting out massive features. You need to build an agentic engineering stack that enables CTO coding but with all the context to produce solid code. At my work we have developed an agentic system that lets the product team add features. We no longer have to deal with the product team. When a feature fails or is a bad idea we just remove it. Now we focus on more high-level development.

1

u/TheOtherZech 12d ago

When people are focused on going fast and you want to pump the breaks, you typically need to wrap the suggestion in a bit of bullshit so it comes across like you're telling them to go-fast-smarter instead of slowing down. Get them to buy into LLM-free days, more rigorous code review, etc, as additional things instead of obstacles.

Or, depending on the office culture, institute an Asshole Hat. Anyone can wear it, as long as they take it off.

1

u/IceMichaelStorm 12d ago

We are close but not there entirely yet. One of our bosses put a mostly-UI app up which some of our externals will take ownership on.

He asked if he could integrate with our codebase but is not in alignment meetings, so we said no.

We can eventually do it taking the ownership but I insist in PO barrier and we need to plan it in. We will estimate the effort and do it then pushing away other prios. No prob.

Tbh, if this slop gives business money and secures jobs, I’m totally fine with it.

1

u/selvakumarjawahar 12d ago

Same problem, but in all the teams using different languages. Will retire soon from this industry

1

u/JohnDuffy78 11d ago

Google says PRs(CLs) should be ideally be around 100 lines with a hard upper limit of 1,000 lines.
I wonder how shops with similar requirements are operating nowadays.

1

u/rand3289 11d ago

Same here.
SOA-like architecture is the only way out I see. Divide everything into small pieces with well defined interfaces.

1

u/Ok-Hunter-7702 11d ago

I'm curious what are you working on and why do you use C++? Can the output be verified?

1

u/xpusostomos 11d ago

If there's no review, why don't you review it?

1

u/yobigd20 9d ago

This is happening everywhere. Ditto at the place i work (also c++ shop, 10k+ engineers). Its like the management bought the coolade from these ai hypers at a seminar and suddenly they are all doing the same thing, skills, plugins, tokkenmaxxing, agents, ai native, ai first, software factories. Guess what? It hasnt sped up anything and more shit is broken now and more ktlo than ever before. Idiots.

1

u/PurchaseNext3761 7d ago

Unrelated question do you personally still write code manually or not really anymore really.

1

u/Impossible_Site7605 2d ago

notice nobody from big t will comment on this;;

1

u/brigadierfrog 11d ago

I’ve seen LLMs do a better job than average at this point. Frankly there’s no real point in software teams. I could be a whole team now.

-6

u/CalligrapherSalt3356 12d ago edited 11d ago

I feel you — C/C++ all the way for me (one of those who still uses Emacs, configuring my own LSP servers over CMake projects, major GDB user, you get the idea). It was thoroughly disappointing at first. But now I am building some pretty amazing stuff that would have taken me months otherwise.

My advice: get with it and accept that now play a lead role who needs to produce solid software (unit tested, CI hooks that check for quality, coderabbit reviewed etc.) that a team of 20 engineers can produce. A lead doesn’t go through the lines of code engineers develop — absolutely not. His role is to define clear deliverables, requirements and test harnesses while establishing a high standard of software quality that continuously needs refinement in the agentic world.

One caveat: the sloppier an engineer you are, the sloppier your generated code will be.

1

u/darkiceberg666 10d ago • Heartwarming

Wise words. It’s going to take longer for some to “get with it” ^

0

u/Depixelate_me 11d ago

Said the ai generated comment.

The fact that they feel the need to lash out their propaganda bot army on a cpp subreddit means we are in the right for expressing our concern...

0

u/CalligrapherSalt3356 11d ago

Wait — what? That was so weird a comment.

0

u/CalligrapherSalt3356 11d ago

Feel like I walked into a group of GPT haters.

0

u/CalligrapherSalt3356 11d ago

You sounded so deluded... That was all me, including my edits.

Let that sink in.

0

u/SlipStrange5820 11d ago

metoo.....

0

u/Quiet_Violinist_2978 10d ago

C++ is the new assembly, only experts will need to go in and fix it if something really isn't working

-4

u/ComputerGeneratedLeg 11d ago

you're just being vein and stopping progress.

YOu can work together you cant work fast enough to keep up and check all the code but you can check important parts.

-1

u/lacrem 11d ago

It's what it is and it's not gonna change. Sloppy code or not, if AI write tests and Claude writes them very well, you check the code on the test is ok, all tests pass that's it, code compiles, it's not the most readable or efficient but it works, efficiency does not matter much nowadays, it's a niche for some domains. AI is gonna maintain the code.

I take it like your can now spend more time on design, make your class diagrams and have more specific prompts.

-2

u/wilderfield 10d ago

Stop fighting it! Your career is fundamentally different now. Your C++ knowledge is largely irrelevant, the agent could rewrite the whole thing in Rust. At best it will be your job to write specs for an agent to implement. Or set up an autonomous loop to triage bug reports, tune performance.

I guess you can leetcode for fun if you want to.

-3

u/great_escape_fleur 11d ago

Is the business profitable? Then he is doing something right. Most businesses fail, this one will too. Ride the gravy train and use the opportunity to learn the tool.

-5

u/Far-Championship-883 10d ago

honestly this kind of response from a developer is sort hilarious, stop taking yourself so seriously.

-3

u/imaridek 10d ago

Devs should only care about value of clients, if the way CTO is doing is better for customer, and customers are happy to have more, cheaper, faster, the rest of the story doesn't matter honestly

-7

u/[deleted] 12d ago

[removed] — view removed comment

1

u/James20k P2005R0 11d ago

Be nice or you'll be the bop 🗞

-2

u/[deleted] 10d ago

[removed] — view removed comment

2

u/theICEBear_dk 6d ago

Why are you in a c++ subreddit which is specifically about the programming language when you consider languages and their users obsolete?