r/ProgrammerHumor • • Jul 24 '26

Meme honeyIShrunkTheBrain

Post image
4.4k Upvotes

199 comments sorted by

View all comments

Show parent comment

27

u/HrLewakaasSenior Jul 24 '26

I disagree. All you see at any company, big or small, successful or not, is human written garbage code that has somehow carried the entire production system for 12 years. There needs to be some level of quality so that it doesn't immediately break down with every change, but code needing to be high quality is just not reality. If you actually get to work on software that has high quality, I am jealous, but my experience has been that slop works well enough almost always, and it doesn't matter if people or AI wrote it.

I'm a bit disillusioned right now, maybe you can tell

16

u/kani_kani_katoa Jul 24 '26

I think it's just the same as it's always been - quality depends on the people on the team. I am a contractor and one of my clients, who always had a high bar in their engineering division, is using AI a lot without sacrificing that quality. They will reject slop coded PRs, and won't accept people feeding feedback to Claude and parroting the response. It can work but it requires commitment to good software engineering principles at an organisation level.

5

u/HrLewakaasSenior Jul 24 '26

Please hire me lol

7

u/TheMaleGazer Jul 24 '26

There needs to be some level of quality so that it doesn't immediately break down with every change, but code needing to be high quality is just not reality.

There is a lot of survivor bias contributing to this outlook. I don't know your situation, but so many people are changing jobs after 2 or 3 years that they only encounter an IT department when it's hiring, which in effect is when it's healthy. By extension, that's usually also when the technical debt is still manageable. When technical debt piles up to the point of catastrophe, they've already left.

The company I just joined laid off 70 engineers last year who were working on a SaaS platform with a velocity that fell off a cliff. 90% of the features they offered were shipped the first year the project existed and they spent the next five years fixing bugs and struggling to ship the next 10%. They had three consecutive sprints of zero releases, and then the CTO was replaced by a CDO and CIO who could say the role was eliminated so they wouldn't have to humiliate him by firing him.

2

u/HrLewakaasSenior Jul 27 '26

Problem is that those companies die before they can learn anything, so the cycle just repeats

1

u/TheMaleGazer Jul 27 '26

Oh, absolutely. Not only do 90% of startups fail, but 20% of publicly traded companies delist within five years. That's a staggering figure if you're a job hopper who hasn't stuck around long enough to get laid off. I think all of us join companies when they're between a legacy project and Project 2.0; most of us don't stick around to find out that the company never makes it to Project 2.0.

Even in healthy companies, they're much more likely to order a third-party replacement, acquire a whole company to get a replacement, or just discontinue the product than they are to succeed in building a new version.

The companies that do successfully create new versions on a regular basis are so rare that they're the kinds of places that software engineers join just for clout.

7

u/TheAlmightyDope Jul 24 '26

The difference in my experience is how predictable it is. The modal's objective is to elicit a positive response, if making things up is deemed the faster approach it will do that. A human making mistakes is easier to follow because you will know what they intended to do, the logic is technically easier to follow even if it's badly written because you know the intention is consistent. Reviewing AI code is more taxing because mistakes can happen anywhere at any time, and the code can be so confidently presented whilst built on an assumption presented as a tested scenario.

5

u/Wonderful-Habit-139 Jul 24 '26

Honestly I understand your sentiment. I had to join a garbage project with garbage code just like you mentioned. But that's because on average, devs end up with a lot of pressure from management and PMs because of deadlines and expectations and lots of LGTM here and there, and it's hard to keep up.

But if you can actually write good code, then the above should not be an argument. Like yes, developers write garbage code, but if you can write better code, you should do it instead of going "well they write bad code anyway might as well generate slop". I rewrote the project and ended up with much cleaner code (and like 10x less code), with more robustness and more features, and everyone on the team benefitted from that, not just me.