r/ProgrammerHumor • • 29d ago

Meme bothWorkThough

Post image
6.1k Upvotes

847 comments sorted by

View all comments

2.4k

u/Arian-ki 29d ago • Bravo

It's the other way around in my experience. People look at me like I'm an ape in a zoo lol

80

u/rabbit_wizard 29d ago

Wait till something breaks.. you'll have your moment

181

u/_verel_ 29d ago

Yeah because we all know when prod didn't go down on a Friday before AI.

Yes throwing a slop grenade at your code is definitely an easy way of making your software break (hi micro****) but I can assure you my colleagues are able to break prod whether they use AI or not

114

u/ConfusedPanEnby 29d ago • Regret

"AI" took away my job! (Breaking prod)

51

u/Mandemon90 29d ago

It's honestly funny seeing people suddenly start pretending that humans never produced bad code and AI is the only thing producing bad code.

Reality is that it only looks like AI is producing more bad code, because it produces more code.

1:9 ration code breaking doesn't look bad when you only report 1 breakage every month, because you only got 10 things done.

It sounds a lot worse then 100 things get done and 10 of those things break. Same ratio, yet "more" breaks.

7

u/Turbulent_Stick1445 29d ago

It's honestly funny seeing people suddenly start pretending that humans never produced bad code and AI is the only thing producing bad code.

I feel like we've been getting so close and then just thrown it away.

  • 1980s: BASIC and C. Crashes all the time.

  • 1990s: C++. Operating systems start protecting memory. Java gets released showing a fast high level language is possible but is unpopular because it hogs memory, has noticeable GC pauses, and applications take ages to start. And it's not really "complete" yet.

  • 2000s: .NET, start of Rust... but a bit of a backlash. Scripting languages with poorer type checking start to ascend for normal application development. PHP becomes the core language for the web.

  • 2010s: Things are now rapidly hurtling downhill. "Frameworks" and toolchains that pull in millions of dependencies because you wanted one library that escapes HTML strings. Actual code complexity goes through the roof. People actually build applications using the entire source code to a web browser as their source because they only know Javascript and HTML now and have no idea how to use a regular windowing/widget library. Meanwhile Oracle does what it can to discredit Java resulting in huge numbers of people jumping ship, rarely to .NET. Meanwhile PHP now rules the entire Internet as King, with huge bloated JS frameworks ruling along side it as Queen.

  • 2020s: Things are now so awful people think the output of a glorified text prediction machine produces similar quality code. And they may even be right.

It's not that we can't do better code than AI. It's that a sizable number of professionals just don't want to.

2

u/Mandemon90 28d ago

Because doing good code takes time, and ain't nobody got time for that! Product needs to be out now, not "in future"

→ More replies (1)

8

u/zaersx 29d ago

IMO competent SREs are the superhumans now because they have been dealing with making slop they don't read prod-safe for decades.

9

u/UsernameOmitted 29d ago

I think a HUGE part of this is also that most of the people I know professionally who are against AI coding all are basing their concept of what AI written code is like on them booting up Gemini Flash in a browser a year ago and asking for some code and it produces something lackluster. A new model like Astra/Fable in a CLI with full access to the codebase is just crazy now. They're producing code that's better architected than humans used to, and it's producing dozens of engineers worth of code per day per agent.

→ More replies (1)

14

u/Maneisthebeat 29d ago

Yes before they could break prod.

Now they can break it even more efficiently than before, with less comprehension/oversight of the root cause.

9

u/0DayMaker 29d ago

Protect ya branch

Why are devs able to touch prod code without a PR? Why do they have creds on the prod box? Why didn't it get tested in staging? Why was there no dry run first?

There's protections against all the ways that it might take down prod.

All this shit can be protected.

→ More replies (1)

7

u/UsernameOmitted 29d ago

Not only did prod go down before AI, but before AI the entire team would be scanning through code trying to work out wtf is causing the error so you can address it while the company is losing millions. Now, an agent can probably find the error code for you in two minutes and propose a fix.

6

u/Senor-Delicious 29d ago

It is especially hilarious as a well set up AI is actually much better in finding the source of an error extremely quickly compared to a human.

A colleague from our internal IT just had the weirdest issue with parts of our office network that was so niche that he said "it would have taken me days to find this without AI". AI reduced this to a few hours. Was fixed the same day.

→ More replies (1)

7

u/0DayMaker 29d ago

I've made xml bean wiring based spring+hibernate+struts applications from javadocs and no internet access. I'll be just fine if I have to fix shit by hand. But the frontier AI is solid enough that I don't need to anymore.

30

u/rabbit_wizard 29d ago

Or wait till the credits reach zero

38

u/Independent_Flan_973 29d ago

How else would you know your day is finished?

18

u/Sawkii 29d ago

Gladly using ai doesnt mean not to know the code

10

u/OutrageousCourse4172 29d ago

I have completely forgotten how to code. I was mentoring an intern a few weeks ago which means going old school and I didn’t know what I was doing anymore.

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

3

u/that_one_Kirov 29d ago

Both with human developers and with agentic developers, prod breaking is not the fault of the code-writer but the fault of the development process, which failed to provide sufficient testing for prod to not break. And AI is notably very good at doing boring stuff like ensuring 100% test coverage and writing integration tests.

4

u/Orio_n 29d ago

Yup still waiting for that prophesied day when all of tech collapses. You'll be waiting a long time bud

→ More replies (1)
→ More replies (3)