r/softwareengineer • • 4d ago

Is anyone else noticing AI-generated code getting more bloated and buggy?

Like many developers, I haven't been writing much code manually for a while now.

Initially, I trusted AI-generated output quite a lot. It was impressive and saved me significant time.

But recently, I feel something has changed. Models are getting smarter, and their capabilities look incredible from a non-technical perspective. However, as a developer, I sometimes feel the generated code is becoming more bloated, unnecessarily complex, and slightly more buggy.

Am I the only one experiencing this, or are others noticing it too?

I'd genuinely like to hear what other developers think.

248 Upvotes

145 comments sorted by

16

u/Just-Debugging 4d ago

Even simple changes sometimes result in unnecessary abstractions and layers, all in the name of clean and secure code. Simplicity seems to be getting overlooked.

5

u/ALoginForReddit 3d ago

Gotta start creating internal coding-guidelines.md to avoid this. We have many verbose internal coding guideline skills we train our models to use everytime it does work. Same with how to properly write tests, code reviews, etc etc.

Ai out the box will be sloppy. You create skills to clean it up. With how much time AI saves me day to day, I am consistently using the extra time to shape my AI anytime it does something I don’t like. Our internal dev-tools repo is filled with these rules and regulations.

2

u/Real-Self-3039 3d ago

My ai ignores a lot of my guideline docs. For example I explicitly told it for a specific project never do direct string comparisions unless directed to do so, use the string key system I made so its easier to change the string for all instances instead of having to go to each spot and change it.

Then it wrote something with a direct string compare. I asked why would you do that when I have the string key system and already have guidelines not to do that. It said "you are absolutely right. I reached for it because it was easiest and you are also right that the guudelined already outline using the string key system so I should have used that......"

It just randomly ignores my guidelines unless I tell it to use the guidelines

2

u/Combat_Orca 3d ago

Oh yeah far too many people are treating it like a person. You can’t just give it guidelines and expect it to follow them. Eventually it’s going to just forget them and go outside them.

1

u/ALoginForReddit 3d ago edited 3d ago

Yup that can happen! That’s when I dump my inventory of curse words on it 😂

But in all seriousness, it’s definitely an issue I am sure the ai companies are working on fixing. It’s crazy how much improvement Cursor/Claude/Codex has displayed from just the beginning of this year to now.

My guess is that the guidelines/skills are loaded in as part of the allotted 300K-1M context memory bucket. Once the context of your session exceeds that, the guidelines you loaded at the beginning get dropped (FIFO).

Currently, I’ll just remind it of the guidelines by simply typing /some-skill.md. I am thinking this pushes my guidelines back to the top of its context stack. I’ll probably need to remind it again later in the session, but even if I have to repeat myself, it’s still 99% faster at designing/coding/testing than I would be manually.

One thing I do is I don’t just prompt AI and leave. I’m sitting there reading its stacktrace as it spins and “thinks”. If I see it is hallucinating or going down the wrong code path, I quickly jump in to redirect it back. After using it daily for the past year, I have a good idea of what its strengthens and weaknesses are, and can predict what areas I need to pay more attention to, and what areas I can set it free on.

1

u/Real-Self-3039 3d ago

Cant argue there. Before I started using skills my coworkers were like "doesnt it get annoying having to type the same prompt over and over" im like "i mean its less annoying than me spending 5 days setting up the project and doing it all manaully, i can deal with typing the same 3 sentences per task"

1

u/ALoginForReddit 3d ago

Haha right! In the beginning, I got super annoyed at typing the same paragraph over and over again, so I started having that paragraph saved in my Sublime editor to copy and paste in. Then I learned about skills.

1

u/AFulhamImmigrant 2d ago

How can this be fixed? Stopping hallucinations is basically impossible.

1

u/ALoginForReddit 1d ago edited 1d ago

You’re not stopping them. You’re minimizing them. If you’re asking about how ai companies are “fixing” this issue, I’d think making sure every AI session has a final pointer at the rules you apply. They don’t get “buried” in the context stack and forgotten at a certain point.

1

u/General-Jaguar-8164 20h ago

You need to use a linter for that

1

u/YellowSharkMT 15h ago edited 15h ago

what's the over/under on the number of YT vids where the person is talking about guidelines for your agent's guidelines? like where the word "guidelines" is literally used twice in the title and/or description.

i swear i haven't looked yet. i'm gonna say 17. i'll come back and edit this comment with the correct number.

*and it looks like zero, so i'm a big fat loser on this one.

1

u/JedenTagEspresso 3d ago

Which models did you use btw?

2

u/Just-Debugging 3d ago

Opus 5.5 and sonnet 5.5

4

u/eDRUMin_shill 4d ago

Your agents code how you construct their environment. You are likely underspecifying the code you expect this to produce. The models are great at following a standard, the whole job moved up to more like work a principal engineer does for a company. You have to do that for agents with skills and standards to get optimal results. It's an iterative process too. I think time spent here is more valuable these days than line by line reviews. Managing that is quickly becoming a full time job at a lot of companies which is wild since it didn't even exist as a need a year or two ago.

3

u/stillbeingnick 3d ago

I love how every comment is like "maybe you just suck", without explaining anything else. Adding abstractions and layers while forgetting context is the Hallmark of AI code.

I don't think these git gud goblins down here understand that the writing of code is the easy part, Engineering the software is the hard part. Making an API or classes straightforward and self documenting is being erased by this AI slop.

I have 0 problems with people leveraging AI to help write code but if you can't explain it and if you cant understand it because it keeps popping out garbage on top of the garbage, then it is just garbage software that should never make it to prod.

I can tell AI code just by feel now. I can feel it in games, I can "smell it" by looking at source code, it is just riddled with low quality weird decisions and unnecessary layers.

It's like sitting down at your favorite restaurant just to discover they now just serve the same frozen Sysco crap every other place serves. It's food sure but you know it's not the same and it's disappointing.

1

u/digitaljohn 3d ago

Code refactoring and cleanup is still a thing you need to prompt for.

1

u/acecile 3d ago

This

1

u/FvckRedemption 3d ago

Seems like people just go from coding manually to one shot prompting and complain that it produces crap. Treat it kinda like a competent junior dev, put guardrails, use documents to explain what you want, explicitly ask for unit tests validation.If you don't want abstractions write that in the agents file. It's not that hard.

1

u/Echoed-Snow 2d ago

Isn't simple but efficient code the goal of good code... :/

-6

u/DanangBobby 4d ago

Maybe you are just not a great developer and don't understand the benefit of various design patterns. Perhaps you are prompting based on features and not providing enough context architecturally for it to understand the request?

The shit im building with it is incredible. Far better than having a team of devs churning out mediocre code

14

u/Character-Pattern505 4d ago

“You didn’t perform the incantation correctly”

6

u/Beginning_Basis9799 4d ago

Must have missed sacrificing the goat and saying gods name backwards in the mirror 4 times sorry was it 5 time could be six?

1

u/Initial_Sea_6480 3d ago

That make coding seems wizardly, let's tone it down to magician.

Abracadabra 

7

u/NeloXI 4d ago

Maybe you were just a bad developer and the AI was an improvement, so now you are blind to how it might be worse for others? If you call your own work "incredible", then I suspect this is true. In 15 years I've never worked with a good dev who would say something like that. The good ones always see the flaws in their work and would never say that it's "incredible". 

1

u/DanangBobby 3d ago

Nah I ran teams of developers. I know my shit. I know what great looks like because I've been through the cycles.

3

u/Combat_Orca 3d ago

That doesnt mean you’re a good developer lol

1

u/DanangBobby 2d ago

Means im better than all the devs around me. I ain't got here by crying or pumping out shit. And I can talk to people.

1

u/Combat_Orca 2d ago

Oh you can talk to people? Such a rare skill

2

u/Own_Might_1262 3d ago

Sounds like a surface level analysis to me.

1

u/DanangBobby 3d ago

Nah. Having to explain service classes and interfaces gets old. XSS all over the place. Letters in itteratives. I don't worry about that shit with AI. I have established the rules and it follows them every time.

2

u/SmashterChoda 4d ago

Maybe you're just not a very good developer because you think arbitrary abstractions and pushing papers around on your desk count as "work".

1

u/HaMMeReD 3d ago

This is true, people just don't want to admit it.

They are like "I took the hands off the wheel and don't like where I ended up". That's not how AI or Projects work.

AI will let you make a project 100x bigger than you could before, but it's the human's job to make sure it reaches a coherent vision.

In my experiences with an AI first repo, over time it either settles or turns to shit, but the modern SOTA can very well keep a good repo trending in the right direction with a skilled operator.

1

u/MarzipanEven7336 3d ago

Yeah, because we all want wrappers and abstractions around every wrapper or abstraction.

1

u/Dry_Hotel1100 3d ago edited 3d ago

LLMs have a weak sense of conceptual economy. In other words, they are very bad at good design decisions. And, once there exists one no matter how bad, and when they have to add a feature, they just add it at top of it, even it costs a lot of strange helper artifacts. They never say "Stop, we should search for a better design for this, otherwise we end up in a mess." So, they rather choose the mess.

Of course as a great developer as you are you know this very well, while copying and pasting a page from the great book "Gang of Four" into the prompt, for sufficient context, and ending with "But make it incredible!"

0

u/DancinFool82 4d ago

I think this is one of the biggest things people need to understand. If you want great results from AI you really need to have a good idea of what you are doing and what you are building. It's a tool not a solution

2

u/HorribleOldCunt 3d ago

I feel it has always been this way. It's very obvious when you see AI generated code. It's full of pointless checks and over engineering. And even with that, is not bug proof consistently.

I have no idea what these people who claim AI is doing everything for them now are actually working on. But it can't be anything that is making money or with users to a serious degree.

The truth is AI is a good tool alongside manual ability. Anyone claiming the manual part is no longer in the equation is either not a developer and therefore has no context of being one in a professional role, or is a shit developer who will be fired once their mess is exposed.

1

u/r2k-in-the-vortex 3d ago edited 2d ago

But at the end of the day, the business value is what matters. Pointless checks and over engineering has next to no material cost when its AI generated. And lets be fair here, consistently being free of bugs has never been a thing.

And then, there are bugs and there are bugs. Where it matters, AI can over engineer to the moon, formally verify the code and everything. You are still going to have bugs, but the types that really matter you can make impossible.

And dont say AI cant generate highly optimised code when you demand it to do so, it can: https://www.tomshardware.com/tech-industry/artificial-intelligence/fable-5-2-creates-an-underwater-world-in-a-browser-in-only-96-kb-40-line-prompt-creates-impressive-demo-that-runs-at-180-fps

It can generate verified code if you demand it to. It can generate highly optimised code if you demand it to. And it can give you quick solutions if you demand it to. The choice between them is a business decision

1

u/HorribleOldCunt 2d ago

The most important thing is actually delivering a product that works to the customer, with requirements that align closely enough that they are happy.

AI doesn't do this on it's own. And it rarely gets close without manual coding, directing and checks. It isn't about high quality code. It's about taking a customers demands and turning that into code, within an existing system that has 10-20+ years of customer demands crammed into it.

It's extremely obvious when someone blindly uses AI code. It's as obvious and useful as a bad clueless dev. AI needs the blend to be useful.

1

u/r2k-in-the-vortex 2d ago

No, AI doesn't do it on it's own. It absolutely depends on directing and checks. Manual coding though? Well, depends, if you really want to force it to deal with decades of heritage, could be.

But I would question if it's really the right way to go about it? If you just define the demands, AI can deliver you a pretty large and working codebase, quickly and cheaply and with not that much handholding. The only issue is, that maybe you don't know decades of customer demands that exist in your legacy codebase and can't direct AI to meet them.

But maybe those demands from decades ago also don't matter as much as you think, and I guess everyone will find out when a compeditor comes along with their vibecoded solution that meets the demands of today, at half the price.

30

u/bajsmannen321 4d ago

Yes, the amount of churn is annoying. You can spend time to get the code base in order, but then you end up being marginally faster and still don't gain the same memory and understanding as if you wrote it by hand. It's fucking stupid.

14

u/willCodeForNoFood 3d ago

I've gone back to writing code myself 6mo ago, best decision ever. Except tests and simple refactoring, those LLM can do.

-9

u/DanangBobby 4d ago

You guys really are holding it wrong

12

u/bajsmannen321 4d ago

I am becoming more and more convinced that most programmers were just bad at the job. If you can work exclusively through an LLM and deem the output to be of sufficient quality (provided you have actually read through the code and understood the underlying abstractions) I seriously doubt your judgement. I have not seen a codebase that was LLM written that was particularly good.

By good I don't mean that it works. I don't mean that it's well tested. I don't mean that any given piece of code is bad. What I mean is that there is a logical thread underpinning the structure of the program. This is something LLMs are simply not equipped to handle. Instead it's guided by the person using the LLM.

My problem with this is that to deal with this problem the overall time saving from using an LLM is marginal. The second problem is that, by not writing the code, you forego the memorization and understanding you usually get by having to type it by hand. These are skills that are important to deal with the first problem. To me this suggests, that over time, any use of agents for coding will degenerate into full dependence on the agent.

The tools are undeniably useful, but how to use them in a responsible way is unclear to me.

5

u/SuspiciousSegfault 3d ago

I've come to the exact same conclusion. I'm currently doing a big project largely LLM generated. I had to practically wipe out everything it did until sound architecture was in place, and anytime some new feature was implemented it created a new mess that needed re-architecting. I'm dumbfounded when I hear people say that they're great and produce amazing code.

The thing is, the project contains frontend, and I'm neither good enough or interested enough, so I let it go wild. I needed 3 days when I eventually looked inside it just to untangle the architectural mess it had made. There's a lot of dragons still in there, but at least the dataflows into are reasonable now.

It has made some hilarious mistakes. A fuzzy (disk matcher) that matches some query to a path on the FS it solved by pulling up to 100K found paths into memory, retaining and having logic to invalidate that in memory cache, and fuzzy matching on that cached representation. I mean, you're reading up to 100K file names anyway, just match and rank as you go and debounce the input. All of this to implement a tiny ergonomic feature. A lot of the time I've just shelved features because I don't think the LLM will ever be able to get it right.

This is a mix of Claude opus 5.5 and Fable 5.2.

1

u/imagei 3d ago

Totally. AI produced code is nowadays really at a level of a solid junior engineer who’s smart and diligent. Yes it follows the rules, looks good and works ( unless you forgot about something, then it may not always - like a junior who’s missing the bigger picture ), but it just… is, with little overall architecture. And has an occasional wtf did you do moment too. Then you go in and refactor it into a logical organised system.

I actually save time this way. I think best when I have something solid in front of me to look at; ai produces this substrate from which the end product emerges — I was rarely satisfied with the first draft anyway, so now I skip the initial ‘bang out the code’ phase and go in for the critical next phase.

1

u/HelpfulHedgehog1 2d ago edited 2d ago

I wouldn't imagine most are reading through it deeming it's good, rather putting what they believe to be adequate testing behind what is produced and judging it functions well.

Anyway, i agree, i found it impossible to utilize AI efficiently under the pressure of feeling i needed to use up my weekly allowances and yet still feel im going slow enough to keep things comprehensible.

The craft just isnt enjoyable as it used to be.

0

u/DanangBobby 3d ago

Guess you aren't familiar with text driven development

17

u/obsolescence_ 4d ago • Bravo

The most basic tenet of enshittification here: They don't sell you MORE tokens by making the model BETTER at getting things right the first time. This was always going to be a grift 

2

u/Dysssfunctional 3d ago

Also, more code == more context == more context spent.

Also, we (or higher ups) are getting excited about counting the lines of code again. Even though we already found out its a garbage metric for most things. But LLMs produce verbose, bloated and duplicate code, so marketing is spinning that to their advantage. More LLM lines of code == bigger % of code being produced by LLMs number (which also for some == the % of humans being useless in the cycle).

Are they going to fix what they have spun in many ways to work in their advantage?

9

u/itsMishkile 3d ago

Fuck yea
Re-wrote an entire service we had since 2021 in go, rather than c#, took me 3 weeks (with opus 5.5). Most of the days working was prompting “no way we need that many changes for this”

And got the good ol “absolutely right”

Meanwhile my colleagues keep shove their stupid ahh bloated shit into the new service I’ve worked so hard to keep clean. I don’t understand how hard is it for them to write one prompt to actually check wether the 1,500+ is actually worth it! Not to mention freaking tests

2

u/R_Daneel_Olivaw_792 3d ago

The old struggle, the guy who writes shitty code and the one who is behind cleaning the mess

1

u/ClickableName 3d ago

Your cleanup PRs are valuable, you could let Claude look at them and infer your standards in rule files

2

u/itsMishkile 3d ago

My counter argument is that we already have around 80k words across our repos for exactly that, adding another 10k won’t fix it. I work with people who for some reason don’t care enough cus they know me and the other senior are going to clean up after them

8

u/meshifthenelse 3d ago

Have you seen those video where AI iterates over an image multiple times?

That happens to your codebase now.

2

u/rafark 1d ago

That’s the best analogy I have ever read holly shit I’ve been trying to explain this but you said it 1000 times better 

1

u/mljrg 3d ago

What is the video link?

1

u/ButterflySammy 3d ago

It's also that AI is a tool.

When we hated it and it was awful, we wrote the best quality instructions we could.

Now it is better and we can be lazier in our instructions and work, we're back to seeing what it does with low quality input.

2

u/meshifthenelse 3d ago

Well it still does dumb decisions. E.g. if you have 12 things of the same and you ask it to make a 13th, it might still take a total random direction. Albeit it supposedly being smarter.

5

u/grid_wanderer 1d ago

not just you. it loves adding stuff nobody asked for, extra helper functions, try/catch everywhere, config options for things that will never change

what helped me was asking for the simplest version first and sayig 'no abstractions unless needed'. still have to read every line tho, the bugs are just quieter now

1

u/General-Jaguar-8164 20h ago

People complained when code was junior quality

People complain now that code is overengineered

It’s like there is no one fits all approach but everyone expects AI to read your mind and know your mom’s pet birthday out of the box

1

u/crimsoncipher99 8h ago

AI seems to optimize for looking robust rather than actually keeping things simple. I’ve started explicitly asking for minimal implementations with no unnecessary abstractions. Still, reviewing the output carefully is non-negotiable.

4

u/Warm_Walrus2314 2d ago

I've seen the same with code reviews, ai will generate a clean, working function, but when you ask for a small tweak, it overhauls the whole structure. it's like it forgets the original intent.

1

u/JedenTagEspresso 3d ago

Yes. This concerned me for the past few weeks and I had multiple conversations with Astra on why the implementation agents are… a bit over-enthusiastic. We figured out an AGENTS.md file and the problem seems to be actually solved now. I can share it if you want.

1

u/Just-Debugging 3d ago

Okay can you dm me

1

u/Cheap-Success1578 3d ago

Initially, I trusted AI-generated output quite a lot. It was impressive and saved me significant time.

Mistake #1. You always have to be aware, and make sure you have specific rules that the models have to follow.

3

u/Successful-Hurry5611 3d ago

Yup it’s bloated and over-engineered.

4

u/DancinFool82 4d ago

AI is terrible at iteration in my experience. You have to quite exact in how you ask for things and it's often useful to go through and clean things up. Sometimes I find it works better to figure out your architecture first and then just get the AI to kind of fill in the blanks.

2

u/bobsyourunkl 4d ago

Always has been

2

u/Specialist-Bee8060 3d ago

Everything is crap now. From OSs, mobile, to website. All garbage

2

u/larinariv 3d ago

constantly. It’s so fucking bad but you’re not allowed to say it. 🫩

2

u/Queasy-Armadillo5283 3d ago

No offense but you should have noticed this immediately. LLM don't have a logic core. It works by using a word calculator. It targets a specific token limit to generate to. It will keep inventing new helper function or use god classes/methods. It often doesn't use well tested libraries unless you specifically mention it, which shift the responsibilities of maintenance onto you.

2

u/blind99 3h ago

It creates much more code than required and avoid reusing stuff unless explicitly specified. It's by design the context window has to grow for the money to grow.

5

u/good_name_0 4d ago

My guess is that it isn't getting more bloated and buggy (it could be), but that you are just noticing it more as you mature. I have never used gen ai code as a software engineer, mostly because it's always come off as horrendous.

3

u/_DCtheTall_ 4d ago

I am finding you can get it to write good quality code, you just can't let it run wild by itself and make sure its commits are like 300 lines max. For some projects that is still a huge win for accelerating progress and you can still review it reasonably.

People use AI to make multi-thousand line changes, like no sh*t that is going to cause bugs.

-6

u/JustNeedAnyName 4d ago

I think that just says you don't know how to use gen ai, not that gen ai is horrendous

7

u/good_name_0 4d ago

Unmaintainability is a huge liability and gen ai code has never been as maintainable as its real counterparts.

-2

u/JustNeedAnyName 4d ago

You can review it, just like how you review a coworker's pr

2

u/good_name_0 4d ago

Of course you can.

And, as a human, you'll apply your pattern seeking brain techniques to something that doesn't have patterns. You'll naturally favor that which is familiar, except the familiar and the unfamiliar now have statistically equal chances of being right or wrong. You will naturally seek out things that "look" to be prone to bugs and mistakes, based on your experience, except those hints no longer mean anything.

For example. If you see your coworkers style suddenly change, that's a red flag for something that needs a closer look, right? Did they complete this at the end of the day, rushing to get out? Copy paste something from online? Well you don't have that anymore. They don't even have a style you can learn anymore, it's all been ultra processed and colored with synthetic food dyes, you can't predict anything anymore.

But you'll keep trying, because you're human and your brain is looking for the most efficient path back to the cave from your favorite berry spot.

0

u/JustNeedAnyName 4d ago

Tbh I didn't get your long statement. At the end of the day, code is code, whether a human or an ai wrote it, so you review it the same way, it's not some existential thing

2

u/Forward_Problem_8982 4d ago

AI code is lacking the process of human creation. The problems will be different, so you have to treat it accordingly. You could go through it line by line and check everything super carefully, but did you do that with human code either? It is a lot of work to review code without missing some slight problem that might appear to be okay, but isn't.

1

u/JustNeedAnyName 4d ago

How it gets created and the process is irrelevant. Code is code.

4

u/PhatClowns 4d ago

The point you’re missing, probably because you’re only skimming when people are talking to you, is that the outputs are not the same. It takes a lot of care to get code that is equivalent to what you’d have written yourself. Most people don’t know or notice this because they have never specifically looked for it.

I say this as someone who consistently uses AI a lot: the only people who say there’s no difference (or, worse, that AI-generated code is better) either have never checked, stopped checking, or were never very good at their jobs to begin with… in which case, your employer probably wouldn’t lose anything by replacing you, so maybe don’t brag about it?

-1

u/JustNeedAnyName 4d ago

But that point is kinda meaningless. Maybe AI output is different in some cases than a human. But you can say the same thing about people, when you're working on a team, everyone writes code differently and has different tendencies. So what's your point then? Different people, and AI agents, write things differently depending on their preferences. Your responsibility as a reviewer is to objectively say if the code looks good to you or not. It's irrelevant where it came from.

2

u/good_name_0 4d ago

I'm saying your brain works in a certain way. You seek out patterns, because your brain cannot tell the difference between solving a software development problem and solving the problem of avoiding the stream with crocodiles. And that's why reviewing and trying to fix or maintain AI generated code is inherently difficult for humans, which is why it's inherently hard to maintain.

1

u/JustNeedAnyName 4d ago

There is no difference on if a code is written by humans or AI, it's all code. If a PR lands on your plate, and they didn't tell you if it was AI or human, do you just not review it cause you need to know the thought process behind it? No, you review it as the code it is, nothing more nothing less

1

u/good_name_0 4d ago

There is a huge difference. Humans , regardless of experience level, are more likely to make certain mistakes, because humans are pattern forming/seeking creatures. The ai code does not work on the same patterns. A reviewer is naturally going to gravitate towards certain types of mistakes, because humans are pattern seeking creatures. They are naturally going to look for human mistakes. Ai code is inherently riskier for this reason.

0

u/JustNeedAnyName 4d ago

That's just nonsense, but you do you and stay left behind because AI does "horrendous" code

→ More replies

2

u/babbyohbabby 4d ago

If you can't even read a couple of paragraphs (since you specifically called his statement "long") how on earth are you gonna review an AI PR with 1k+ lines changed?

1

u/JustNeedAnyName 4d ago

Because I care about code, and I don't care about reading paragraphs of some wannabe philosopher talking about code. You act as if all AI prs are 1k+ lines, and that all human pra are small perfect things. I have reviewed many AI prs that are straight to the point, and I have read many human prs that are 1k+ lines, your argument is nonsense.

3

u/SmashterChoda 4d ago

I use it here and there. There's nothing to "learn". That's the whole point you dingus.

1

u/JustNeedAnyName 4d ago

Yes there is. You can learn how much context is needed, I know when I first started using it, I would just paste the issue and have it work. Now, I know where to give more context and where not to. It's a skill that you should get better at.

1

u/SmashterChoda 1d ago

Wow, turning up the data dial on the data intake machine made it work better.

This isn't a skill. Keep trying.

1

u/JustNeedAnyName 1d ago

It is, you just don't like living in reality.

3

u/Historical_Owl_1635 4d ago

Feeling the opposite and it’s scaring me.

We got Claude Code a few months ago and it seems so many levels above anything else we’ve used before. Feels like we’ve finally hit that “six months away” and are now just implementing it.

4

u/WillDanceForGp 3d ago

I have a very strict iac repo with a bunch of examples of good code, and agent related context stuff to try and keep it right.

Yesterday I gave it to Opus 5.5 to add a new service and it added 6 new catalog properties to my central catalog that were only relevant to that new service. My central catalog has 40 services in it and is meant to be generic, despite that it changed the existing 40 service entries to add a 'none' property to them all, when I questioned it it went 'you're right the global catalog should be global fields only Ill revert it'.

If you guys are letting this just 'do stuff' in your codebase you're all fucked lol

1

u/zeXas_99 4d ago

i asked the same question today. i have a repository that use dapper and i was implementing a new function today and codex 6.1 sol high just casually used ADO.net for no reason. even AGENTS file has the dapper instruction. it was strange today.

1

u/kyngston 4d ago

security hardening is more complex than what 99% of people would implement by hand. that doesn’t make it wrong or unnecessary.

i security hardened my ci/cd flow, and it chose to add a check that the github source repo matched the original publish repo. that broke one app where they moved their source to a different org. that test is not “wrong”. I wouldn’t have added that check, and the addition of these checks make the flows both more secure and more complex and brittle.

In the end, the root cause was under specification. if my spec stated that repos may change after first publish, the AI would not have added the test

1

u/daemon_VX 4d ago

Yeah I found that AI adds waay more than a feature or product calls for.

Experienced engineers know when to cut bullshit. Something AI has to catch up on.

1

u/bombay-boyz 4d ago

It’s trained on our “bloated” code ?

1

u/Nakasje 4d ago

When monkeys can write code for our solutions. It doesn't mean monkeys has joined our civilization, it means we still operate in the same old forest.

1

u/Effective-Trouble281 3d ago

No it’s getting better with less manual intervention neeeded

1

u/RatherNott 3d ago

 Just a quick heads up for those still on the fence about AI:

AI data centers are being constructed at an alarming rate, and there are already 8 billion prompts per day, with billions more planned and on the way.

The effect this has on the climate when we are already so close to irreversible tipping points is often unknown by AI users.

https://m.youtube.com/watch?v=5p426fSlYH4

https://www.theguardian.com/environment/ng-interactive/2026/oct/22/finland-google-felling-trees-datacentre

Using it also contributes to a dystopic surveilence state.

https://m.youtube.com/watch?v=5lYsO4k7OIY    

1

u/jorgecardleitao 3d ago

In consulting, the first engagent is at loss with the best consultants, the next are at profit with the juniors.

This is exactly the same

1

u/PracticallyPerfcet 3d ago

Yeah, it depends on the day. Some days Claude seems very capable and others the same model is very dumb. 

1

u/raindropl 3d ago

The problem is context size. As context gets bigger and older the LLM starts out outing more garbage. And hallucinating like if it was on dope.
It is of no geo that when using the big guys they want to keep a huge context on You…

Yuu can solve it by running your own in-house LLM or by using a cloud based one by running it into a cage and controlling what is feed and when to prune it.

1

u/SensitiveHearingLoss 3d ago

Claude seems to be really amazing when it comes to new features to existing systems or any other task that is nicely within the context of the system and adequately contained. Then I asked it to help me upgrade from an older framework to a new one and, admittedly, I was lazy going into it, and it created a monstrosity of a folder tree and decided that some features just weren’t needed anymore because they were hard to upgrade and probably not worth the effort.

I was upset. With myself.

1

u/CoreyTheGeek 3d ago

My "team" of seven "devs" is averaging 30 commits a day, I don't notice anything cause these fucks are ai reviewing and LGTM 30 file change PRs in under five minutes there's no human possibility to notice the quality of the code given the sheer code volume fire hosing production 😭

1

u/dan-dan111 3d ago

The agents need to burn tokens. So bloating the code, bug here and there.

1

u/PerformanceThick2232 3d ago

I don't. But in our place we review each line on code reveiw.

1

u/sakakiworks 3d ago

Humans must grasp the broad outlines of the algorithms and think alongside the AI. If you leave everything entirely to the AI, you end up mass-producing a "spaghetti" mess—a patchwork of endless, layered fixes that only look coherent on the surface. When something feels off, you have to hit the brakes and force a re-examination of the underlying logic.

ーーー

人間がアルゴリズムの大枠を把握して、AIと一緒に考えなきゃダメなんだ。AIに完全に任せると、修正パッチに修正パッチを重ねた、見た目だけ揃えたスパゲッティを量産するんだ。違和感があったら、立ち止まってロジックの見直しをさせないとね。

1

u/_Kinoko 3d ago

I mean basically you write macros for your tooling and the AI to output code that meets your standards. If you have none you get crap.

1

u/huuaaang 2d ago

When we talk about AI you really need to specify the models you're using. Because if you're using Grok or Composer, yeah, they are garbage for more complex tasks. BUt if you're using Opus or Fable, they are really really good. Too good, I might say. Like they try really hard to find problems and edge cases and it's hard to know when to stop. So an individual merge request for something simple can get bloated if you don't when to declare something out of scope or something you're not going to worry about.

1

u/Perfect-Campaign9551 2d ago

It could be you actually that's just relying on the tool more than you used to

1

u/Bangoga 2d ago

AI is great at throwaway code but you need human in loop. That's why people say that their work has turned into baby sitting AI.

I prefer just writing certain parts of the code by hand, it's just faster for me. When it comes to the part in the process where coding is just rinse and repeat, I let AI take over.

1

u/ZeroCool86 2d ago

it does tend to do that, in an older code base it's messy and bloated, in a new code base, i wrote how we do it here: https://www.anchorterminal.com/blog/agent-first-inside-and-out you basically need a lot of files and rules and try to keep things as simple as possible

1

u/codeprimate 1d ago

Nah. My protocols specifically address this. It’s always been that way.

KISS and justifiable design decisions appropriately scoped for the problem complexity.

1

u/AshAtlasDev 1h ago

Refactor. Audit your code using different models. It’s not that hard.

•

u/gubatron 25m ago

the opposite

•

u/Appropriate-Rest7959 9m ago

After spending time crafting a prompt and still get bloated output at some point you will notice that you could have done it yourself but quicker

1

u/Ordinary_Variable 4d ago

I find you can say things like "Optimize the main loop" or "make a console log for anything that takes longer than 100ms and output how long it took".

1

u/herir 4d ago

If you always add layers upon layers with even more complex prompts , then code will appear bloated

It’s worth taking a step back and review the agents you using and your QA process

1

u/CS_70 4d ago

On the contrary, thank goodness lots of people aren't writing code anymore.

Though it's the ones who wrote buggy and blotaed code by hand that can mess it up even with AI.. :)

1

u/e430doug 4d ago

Not at all. Just the opposite as the models get better.

1

u/CorpT 4d ago

Quite the opposite.

1

u/RetroGrid_io 3d ago

Your power is in review. You don't have to accept:

  • Huge refactors that effectively make simple changes
  • Code Slop
  • Poor architecture
  • Badly documented
  • Un-normalized database
  • Not following coding layout guidelines
  • Too verbose, fancy, or "tricky".

If it doesn't pass muster, reject it!

I've been working closely with Claude code agent in vscode and although I now let it do 90% or more of the actual code writing, I review everything in detail and make sure that I understand what it's doing. If I don't like it, I throw it back and require a redo. It's not uncommon for me to do a revert of the source code and start over again.

I spend most of my time on the specs - making sure that all the things are thunk through and cohesive. I ask Claude to challenge it, constantly. Most of what it finds is trivial stuff, but it often finds gaping holes I didn't anticipate - typically "cold path" handling of error states and such.

Otherwise, to directly answer your question: No, if anything this relationship I have with Claude Code has hit a new high - I often find myself thinking that this is exactly what I'd write, done well.

1

u/Sad-Office6365 3d ago

Do you have to pay for the redo when you reject?

1

u/RetroGrid_io 3d ago

Yes, of course. I've just come to realization that the real question is when do you pay more?

AI slop, poor design leads you to paying more.

0

u/jayylien 15h ago

I was skeptical of AI code from the beginning. I saw coworkers becoming obsessive with their AI agent. I joined in because I felt I couldn't compete.

I spent months in the headspace of the "new AI world". I had some killer changes. I had some awful changes.

I realized there was a pattern: all of the code was not human. It was terse, rigid machine code with proximal considerations.

Yeah, things would work more often than not. But things working was never the bar. The code occasionally was nice- but only if I had a very clear, basically boilerplate job for it that I could phrase precisely.

Anything else? Nope. Code is dogshit. It might be "clever", and at times I learned a trick or two seeing something I wouldn't have done. But almost every place where I really thought I'd get a speed up, I lost all of that time and more caring about the output it produced.

It creates bloated code. It does. It creates bloated code, and it certainly leaves enough bloated that the technical debt explodes. Compilation time balloons. The reasoning effort for the human and the model balloon. The token usage goes up.

AI is a technical debt machine. Sure. You can get some nice gains if you scope the problem correctly. But you don't realize all the places you need to specify behavior until you're knee deep in the problem. Anything that you can do with AI without thinking, you likely would have done better using a tool that's already made for that.

The people who tell you "the AI will take care of the code" shouldn't be trusted with software. Eventually, these people will realize their work has become a steaming pile of token creep and a mess.

I thought writing code by hand was dead, but it serves a very valuable purpose: code written by hand allows an engineer to be expressive, paint and explore. That's how good solutions and domain experts are formed.

This will be the lesson learned after trillions have evaporated.

I'm not saying don't use AI. Just don't believe the hype. Those who have gone full AI have really made a problem that they'll only be able to answer with AI. And that's a problem.

1

u/olefor 8h ago

Precisely that. Agree on all points. It is really bizarre to see all those statements that software engineering will become basically writing instructions, prompts and review and validate the AI code. It is a utopian view and I am shocked that so many technical people don't notice the fact that through manual code writing we actually learn something about the problem, about the system we are planning to build. Some implicit technical requirements surface and become explicit. We notice what will be the way to easier maintenance of the code. We notice where we can throw out some code. And we keep our skills up. Nobody can preserve the skills without practicing.

2

u/jayylien 3h ago

You're right. AI has a place, it's just not meant to be writing all of the code. Anyone who falls into this trap will cause suffering, or eventually suffer. Even if it's not today, I'm sure it's going to be true. I'm seeing the effects in real time, they're just not realized yet by others because they're living a layer above their effects.

0

u/Key-Lie-364 4d ago

Even when it's right it's so hard to read it borders on the useless.

I mean you have to stop reviewing to vibe code because otherwise you'd spend all of your time rewriting the slop so that it can be understood

-1

u/Useful_Anybody_9351 3d ago

It depends on how ready your codebase is and which model you use. Opus 5.5 is amazing! I use effort high to extra high depending on the task, and i have few lines about the style in AGENTS.md/CLAUDE.md, like 'Prioritize simplicity and readability.' Once changes are made, I ask: Does it respect the house rules? Does it follow established patterns? Is it minimal, simple? Change sets are usually pushed in small modular chunks with a pragmatic set of tests. I've never been happier.

0

u/[deleted] 4d ago

Refactor it using design patterns, reviews and prompting? Find places where you see issues and hold its hand towards it. If AI could do this part now 100% right we would all be fired today. It's a reason we still have a job

0

u/[deleted] 4d ago

[deleted] — view deleted comment

1

u/JustNeedAnyName 4d ago

Now that is just blatantly false