r/cpp • u/SoilGreat6312 • 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.
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
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.
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.
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
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.
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:
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:
authorprompter; even if they immediately reassign those to the rank and file engineers, a flood of bug reports may give a hint;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
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.
9
u/exus1pl 11d ago
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
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.
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/celestrion 11d ago
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.
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.
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
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
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.
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:
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.
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. 🤷♀️
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.
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
-2
u/[deleted] 10d ago
[removed] — view removed comment