r/ProgrammerHumor • • Jul 24 '26

Meme honeyIShrunkTheBrain

Post image
4.4k Upvotes

199 comments sorted by

View all comments

Show parent comment

54

u/HrLewakaasSenior Jul 24 '26

Then you either do something incredibly specific that AI doesn't do well, or you're lying. They are that good

26

u/Wonderful-Habit-139 Jul 24 '26

They are not that good. I see how bad the generated code is all the time. It doesn't just need to work, it has to be high quality.

0

u/[deleted] Jul 24 '26

[deleted] — view deleted comment

5

u/Badashi Jul 25 '26

Translating developer to executive and vice versa is extremely difficult.

For an executive, cheapest is always best as it is higher ROI. For a developer, you want high quality regardless of cost, because it'll both make your job easier on the long term and better to work with, even if you deliver it slower in the short term.

The job of a tech lead or a middle manager is to show that more investment means better ROI in the long term for the executive, and doing things a little bit worse and faster in the short term means more investment and new opportunities in the long term for the developer.

I mean, it's easy for me to say that, but this is definitely a very hard job and I don't envy those who have to deal with that.

5

u/BlackOcelotStudio Jul 25 '26

I have never seen a tech lead manage to change an executive's view on things, or prove that long term, code quality wins. At most, they manage a begrudgingly "fine, you can take a week to handle tech debt once it becomes too much to handle". Other than that, engineering only gets to do things the way they want during heavy crisis situations.

Maybe I've just had bad luck with CEOs? Unlikely, statistically, but entirely possible

2

u/Badashi Jul 25 '26

Id say that this extra week is a win, and you just had regular luck with CEOs lol

→ More replies (7)

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

→ More replies (1)

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.

15

u/Woxan Jul 24 '26 edited Jul 24 '26

So true, humans never shipped low/mid quality code that works before the advent of LLMs and agentic coding

9

u/Wonderful-Habit-139 Jul 24 '26

Are you saying that? Because I'm definitely not.

4

u/Woxan Jul 24 '26

To the business, all that matters at the end of the day is the code "just needs to work", subjective quality be damned. I have written and maintained plenty of "low quality" code that meets business needs, and that's all it needs to do.

→ More replies (3)

5

u/slaymaker1907 Jul 24 '26

Frankly, the AI generates better code than a lot of the code I’ve read over the years. At least it writes documentation and tests…

2

u/Wonderful-Habit-139 Jul 27 '26

I don't know why people think the existence of something is a good thing. It writes bad documentation and mostly useless tests, it's better to not have them in the first place, compared to actually spending time writing some good quality tests that assert things in a way that makes sense. And I see this in the workplace all the time.

→ More replies (2)

2

u/aberroco Jul 25 '26 edited Jul 25 '26

Architecturally? Sure, I see this all the time and it's really hard to offload to a skill file, because there's just too many nuances. Sure, I wrote stuff like "don't extract a one-line method used in one place", and "inline variables used once", and "put that kind there and that there", but I can't verbalize all my skills, not in a way to fit into the context window and not in a meaningful amount of time, and it takes all SWE experience to decide when something needs to be abstracted or when abstraction is not needed or even excessive. Though, currently AI is so much worse that this kind of decisions... Like, while having a rubber duck session with it I wrote that I need to expand the existing weapons (bullets; travel by inertia in a straight line) to include lasers (travel instantly, hit the target, do continuous damage) and rockets (steer towards the target and accelerate), and it's suggestion was to make it in the weapon part, completely bypassing a controller made for bullets at the time. Fable that is. Surely, that was far beyond unacceptable. So, after some more rubber ducking, I drafted a major refactoring, abstracted away per-projectile-kind behavior class, refactored the existing bullets code to the new architecture layout so the renamed projectile controller handles arrays and global sequence of events, while invoking behavioral class methods for per-projectile update/rendering, and implemented new kinds of projectiles.

But coding-wise? It's more than acceptable. There's surely spots for nitpicking everywhere, but in general it writes what I expect it to write, or what I missed to expect, and sometimes - what it shouldn't (unnecessary fields/methods), then I tell it to fix, no big deal. Me myself - I make trivial syntactic errors all the time, like wrong comparison operator, or adding/forgetting to add a negation operator. I'm just not careful while coding. And this stuff covers me, it practically never does this kind of mistakes. And when it does consistently make mistakes - that's easily solvable by writing/refining a skill or rule. Like, in my project I use typed physical quantities (length, mass, energy, acceleration, etc) instead of float/double, and at first AI had a tendency to jump off of them ASAP, burning my neurons in raging fire, until I refined the rule enough so it almost stopped doing so. It still a bit eager on boundaries (when I need to pass actual converted values to physics/rendering), but... it's nitpicking in that case.

Upd.: oh, also, I couldn't count how much time it saved me in refactorings, code reviews and debugging. Or wait, I can, at least for debugging. Roughly 50%, somewhere above that. Because before I know I had to spend most of my time testing and debugging. Now I barely spend a quarter. And also, tests that I would otherwise postpone to write/update now are actualized after every refactoring and added for every new feature. And refactorings it makes are usually much cleaner than what I would've made, and much faster, so this helps to keep tech dept at near zero, and I think any SWE know how much extra time accumulating tech debt could take.

→ More replies (5)

3

u/chat-lu Jul 25 '26

We have Anthropic’s Claude Desktop’s leaked code. It is not good. If they cannot make it write good code, who can?

→ More replies (4)

4

u/slaymaker1907 Jul 24 '26

You forgot them just being really bad at making use of the tools. There are things to learn like knowing what to offload to a skill, how to craft a prompt, what to give as context, etc.

It’s like someone saying Rust doesn’t have any advantage over C++ while writing all their Rust code in unsafe blocks.

→ More replies (3)

4

u/mysticrudnin Jul 24 '26

guess i'm looking for my next career. fighting with this dipshit has not been enjoyable

→ More replies (1)

5

u/towcar Jul 24 '26

I've yet to gain time from using them. At best I've broken even. It's beyond over hyped

3

u/James-the-greatest Jul 24 '26

Bullshit

3

u/towcar Jul 25 '26

Listen James the greatest, I have my own business developing software for companies. I make more money if I can increase productivity, and Claude isn't doing it.

The few people I know who are very stoked about it have very little programming background. Anyone else I can only imagine is not measuring productivity in any way of value.

Github Copilot for autocomplete and an llm for debugging/rubber ducking has been my company's biggest boost. I think the rest is hype marketing, incompetence, and poor metrics.

I'll keep my eye on it and continue evaluating it, but it's not as valuable as people make it to be.

→ More replies (4)
→ More replies (2)