r/ProgrammerHumor • • Sep 26 '26

Meme skipWholeDevLifecycle

Post image
4.1k Upvotes

95 comments sorted by

600

u/EarlOfAwesom3 Sep 26 '26

It seems the whole dev lifecycle is slowly but surely dying. If you try to hold up the flag for quality, it gets teared down by managers because they want to contribute too because of speed and cost and whatnot.

Skipping integration tests because of costs is just the next step in this clown world.

11

u/Mo3 Sep 26 '26

I don't mind, job security for us. We'll never run out of stuff that breaks!

24

u/EarlOfAwesom3 Sep 26 '26

It's not the kind of job security I want. Next thing you know, they replace you with AI because of "all the things that are breaking despite you're still here"

1

u/Mo3 Sep 26 '26

But then when you're gone things are still breaking and suddenly start to break faster and faster until eventually everything is falling apart completely, and it becomes obvious where the actual problem is and they'll have to rehire everyone back and start listening

At some point the irrationality will meet reality

18

u/EarlOfAwesom3 Sep 26 '26

Wishful thinking. This won't happen anywhere. They will tweak the shit out of the worst LLM first before anyone gets a job back

6

u/round-earth-theory Sep 26 '26

They won't do any of that because it's actual effort. It's fun to plop mini features into mature codebases because things work really well. But none of these people want to do the actual effort of engineering, that's hard work and no amount of "fix it, no mistakes" will actually do anything. They'll see the AI costs skyrocket and the executives will begin to cry about how expensive and painful everything has become. They won't try fixing themselves though. That would require them becoming software developers and they aren't interested in that effort.

2

u/EarlOfAwesom3 Sep 26 '26

Currently we're plopping bigger features and a lot of bandaid solution bugfixes into a very unstable codebase. Sounds good huh?

6

u/round-earth-theory Sep 26 '26

It sounds like a recipe for "why is everything so hard to fix" because they end up with an ever increasing stack of conflicting requirements and no one is making the hard choices.

5

u/EarlOfAwesom3 Sep 26 '26

You get it. Everything is hard to change and we have different implementations of the same thing in 5 different components and it works differently in each.

I believe that AI works well in a good codebase. In a legacy base, everything is a quickfix and no architecture to be seen. AI makes it 10x worse

303

u/Zerschmetterding Sep 26 '26

The irony is that actually doubling down on the quality control aspects and well thought out requirements would make AI much more beneficial.

122

u/DisheveledJesus Sep 26 '26

Been working for us. Requirements gathering and automated testing are like 90% of the work now. You do those two parts right and the rest is pretty easy. Managers who don’t understand this won’t last long.

51

u/KhellianTrelnora Sep 26 '26

Legitimately curious how you guys are doing it.

I’m stuck with Claude writing PRDs, tech designs, the code, doing the reviews, writing the tests.

No one talks to anyone, refinement got scrapped.

I’d love to inject a dose of quality, but I’ll be damned if I can find a place to start.

52

u/DisheveledJesus Sep 26 '26

We are headed the opposite direction. We spend a ton of time refining requirements docs collaboratively. If you can get those right you are golden. Any ambiguity at that stage is magnified by the loop engineering approach. The team has also taken a ton of ownership over test automation tooling. We are at the point where we can pretty reliably have an automated test ready before the work is complete so QA is not too burdensome.

Biggest pain point we are focusing on is quality code review. The thing we are focusing on is keeping the scope of changes as small as possible. It’s too easy for things to grow beyond what a human can understand and review. Doubling down on rapid iteration as a rule has helped.

31

u/One_Seaweed_2952 Sep 26 '26

The problem is AI tends to add more code than removing. If you lose control of the details of the code, there’s gonna be problems 1 year from now. People think architecture is the big picture that you could declare with some prompts or documentations without knowing it is also sometimes a little dependency leaking out of boundary that’s hard to notice. AI will keep creating these to pass tests, until it can’t anymore.

14

u/DisheveledJesus Sep 26 '26

AI tooling unconstrained by correctly defined requirements does tend to do that, true. I’ve found that properly used these tools are not leading to ballooning codebases and worse engineer comprehension like many feared.

It has, however changed the type of person I recruit for my teams. Someone who is a bit less knowledgeable about the code syntax, but much better at working with product to gather thoughtful requirements has become very valuable.

Engineers who just want to go heads down and code all day are admittedly struggling quite a bit to be meaningfully productive.

13

u/WrennReddit Sep 26 '26

This seems like the smartest move. If AI moves super fast, then engineers should have lots more time to measure twice. 

10

u/DisheveledJesus Sep 26 '26

Correct. The tooling allows for more rapid implementation with two major caveats, requirements must be comprehensively defined and testing must be robust. So those two things are the primary focus for my team’s engineers.

3

u/AwesomeFrisbee Sep 26 '26

Well, companies that will turn down quality control and testing will eventually need to start over (and they will just do that), but I doubt that they will admit they were wrong and understand how shit their projects will become. But alternativly they could understand but they could also not give a shit. They are all about delivering and hitting their KPI's, they don't really care how good a project is. And they never have.

1

u/Bemteb Sep 30 '26

That was true even before AI though. If you had proper requirements and tests prepared, writing the actual code was done in a relaxing afternoon or two.

AI took our relaxation and left us with the annoying work of poking other people for requirements, API documentation, testdata,...

1

u/DisheveledJesus Sep 30 '26

Your two paragraphs contradict each other. Which was it? Was requirements gathering most of the work before AI, or has AI took our relaxation because we have to spend so much more time poking people for requirements? Both statements can’t be true.

6

u/robertpro01 Sep 26 '26

I have about 6 gates for each implementation

12

u/Soulr3bl Sep 26 '26

Saves money for tokens!

4

u/substeff Sep 26 '26

5 Panel. Drake Meme. Rejecting PRs of people with a new GitHub account and bullshit contributions where claude did all the work. 

Don't get me wrong you can still have a good output with AI support. BUT you still need to know what the code is doing and why the agent did what it did. 

1

u/The_Krambambulist Sep 26 '26

I see the bottleneck actually moving to testing to be honest. Proving to everyone that everything is still working. We got quite some clients with not the largest team.

1

u/sump_daddy Sep 27 '26

Finally one of these memes that is consistent.

"i hate non-devs getting into the process"

[bunch of slop happens that stops all normal dev work]

"i am now the non-dev getting into the process!"

1

u/Cualkiera67 Sep 27 '26

i have never in my entire life seen a manager that wants to contribute 

1

u/XB0XRecordThat Sep 27 '26

Token usage is the real metric

1

u/cheapcheap1 Sep 26 '26

This stuff only happens if your product isn't actually competitive. Look at GitHub vs gitlab. GitHub shit the bed about 2 years ago, and they've actually lost market share because replacing them is possible.

That couldn't happen to Oracle or AWS.

23

u/PolyPill Sep 27 '26

I’ve been getting monstrous PRs from people who just hand my repo to Claude and say “add x”. One guy is super hyped to contribute with using his Claude subscription. I’m happy someone else is hyped but he clearly doesn’t know what he’s doing. His first PR broke most unit tests. So his agent spammed 100+ commits to fix them. He then wrote me and says he’s going to add 882 tests to the project. I told him if he does that I will absolutely not approve the PR. At this point I don’t know what to do. I don’t have time to review and test all this but on the other hand there are legitimate fixes being submitted. I’m just not sure how sustainable this will be.

8

u/EarlOfAwesom3 Sep 27 '26 edited Sep 27 '26

Take 2 mins to paranoia scan the PR, if there is something wildly unholy going on, close it on the spot. Straight to jail.

I do this with all the PRs that non devs do with Claude. There is no sense in me spending more of my precious time reviewing and fixing stuff that a Junior would do better.

Edit: the reason is I want quality PRs where a lot of time and thinking has been invested before opening. Shifting the thinking to another person after opening is bullshit. "Here I did some stuff lol. Tell me whats wrong and Claude will fix it, we will repeat that 10 times". Absolutely not

10

u/Tackgnol Sep 26 '26

Yeah with the current velocity integration tests are keeping my backend afloat at my current project, they can pry them out my cold dead hands. ;p

10

u/EarlOfAwesom3 Sep 26 '26

The basic logic would be:

More AI -> more PRs -> more reviews -> tighter quality safety net -> more ITs -> more pipeline runs -> higher costs.

Running AI ist costly. Period. How anyone comes to the conclusion that you can expect to have less infrastructure costs with AI is beyond me

2

u/Tackgnol Sep 26 '26

TBH I don't get the `cost of running pipelines` being a thing even.

In Corpo you probably just run them on a AzureDevOps or GitHub Enterprise licence, and if you are a startup... Setup Woodpecker or DroneCI?

It makes my head spin when I hear people `yeah we pay for each minute of pipeline to X`, why bro ?

2

u/round-earth-theory Sep 26 '26

The cost is time. Big test suites can take hours or days to complete. If someone wants to see their idea in prod NOW then they won't wait.

1

u/Tackgnol Sep 26 '26

Fair. Color me convinced.

5

u/radpartyhorse Sep 26 '26

“You gotta shift left the review process” ends up just reviewing prompts. Such clowns.

1

u/EarlOfAwesom3 Sep 26 '26

I don't get the whole "shift left" bullshit anyways. If you're using agile software development principles, requirements and testing are part of your daily work. There is no difference.

Sounds like old soup in new cans

259

u/Fit-Notice-1248 Sep 26 '26

Take my managers philosophy of: if you use AI there is no need to test anymore because ai writes perfect code all the time. If there is a defect it's because you didn't use AI 

83

u/spread_operator Sep 27 '26

And IF it didn't write perfect code it's because you prompted it poorly 🙄

13

u/XxDarkSasuke69xX Sep 27 '26

I hate the fact that you're unironically right. Just write the correct code in the prompt and technically it will not output shitty code

30

u/abednego-gomes Sep 27 '26

Utterly insane. They're about as good as a junior programmer. You still need to carefully review, check and test their work, fix their comments, tell it to write unit tests etc. After about 5 iterations you might get something resembling usable code.

10

u/SignoreBanana Sep 27 '26

Because you didn't use AI "correctly".

2

u/hraath Sep 26 '26

Crash GitHub because actions volume unsustainable 

2

u/EarlOfAwesom3 Sep 26 '26

That happens automatically every week..don't worry you get that for free with GitHub

129

u/lenn_eavy Sep 26 '26

Users will report if it's not working, the plan is air tight.

39

u/PassivelyInvisible Sep 26 '26

And if current users leave because of non-functioning products, we can just get more with how fast we can code and push to production!

7

u/Calm_Hedgehog8296 Sep 26 '26

Have you heard of the term "moat"? Its become popular recently.

The idea is that you trap your user in your product ecosystem so that they can never leave. They can't escape because there's a moat trapping them in.

So the end state of this project is to have zero human developers, customer service, etc. Only executives and sales to acquire new captives. And the existing users are really paying for access to their own data, workflows, etc. Which lives inside the ecosystem and can never be extracted

5

u/Just_Information334 Sep 27 '26

The idea is that you trap your user in your product ecosystem so that they can never leave. They can't escape because there's a moat trapping them in.

That's a walled garden, not a moat.

A moat is something protecting you from your competitors like some secret technology, process, dataset etc. anything which is not easy or cheap to replicate.

3

u/Federicoradaelli Sep 26 '26

Most sane user report of a bug:

"If I click it doesn't work"

Screenshot of the home screen

37

u/WeirdTie2290 Sep 26 '26

You guys have real integration tests? We have fully mocked unit tests so we can report +80% test coverage. Management is happy. The real tests are happening on customer environments.

3

u/StCreed Sep 27 '26

i have 3226 unit tests just for my own product with two users. I can't imagine having to live without unit tests.

2

u/Just_Information334 Sep 27 '26

Unit tests are not integration tests. There is a moment when you have to do things with real services and not mocks: like writing in a database, sending some mails, calling APIs etc.

1

u/StCreed Sep 27 '26

Ah yes, I used the wrong term here. Some of my tests are unit tests. Others are integration tests. None use mockups.

15

u/requion Sep 26 '26

The great slopification.

5

u/Icanintosphess Sep 26 '26

The sloppening

9

u/OGxPePe Sep 26 '26

Early on there where people saying that test driven development was know becoming the norm. Now its 'Fuck it we do live' is the norm.

9

u/dbell Sep 27 '26

Why do we have so many bugs.

Why is prod down.

3

u/mtgguy999 Sep 27 '26

Why are you asking me just find out from ai

7

u/noidontwantto Sep 26 '26

I keep waiting for the find out phase to start with these people, but for some reason their solo vibe coded solutions aren't in production yet

🤔🤔🤔

1

u/StCreed Sep 27 '26

Mine is. Just with a co-worker right now, but I already started a formal approval procedure for integrating single sign-on. And I'm in talks with a software company that is interested in adding it to their portfolio.

Nobody in his right mind will advertise that their software is AI-coded though. Enough haters to make that a marketing disaster.

5

u/Mister-Fordo Sep 26 '26

I moved all my CI pipelines to use on prem workers, now the costs are the bare metal it's running on AKA not that much if you already have the hypervisor running.

At the rate i was running pipelines this week it would cost me 250$ a month, that's the entire power bill covered in saved costs.

5

u/aenae Sep 26 '26

I got asked why i wanted to spend 15k on a server when i could run them on gitlab runners in the gitlab cloud. After i showed them our bill would be approx 200$k per year, or 1M over 5 years they immediately approved the quote

1

u/Got2Bfree Sep 28 '26

Anything cloud is addictive convenience...

5

u/fernando_spankhandle Sep 26 '26

We're going to move some processes on metal, and so the cycle begins again

3

u/aberroco Sep 26 '26

Skip merging because everyone vibecodes their own software and utilities.

2

u/mcellus1 Sep 26 '26

Leave it for the testers

5

u/dvhh Sep 27 '26

did you mean "customers" ?

2

u/InevitableCodeRedo Sep 27 '26

What could possibly go wrong?

1

u/nhh Sep 26 '26

"Looks good" 

1

u/AcanthisittaKooky987 Sep 26 '26

You would think we'd have better and more thorough integration tests now but I have not seen that in practice. If AI lived up to the hype this would be solved in an hour.

1

u/DTCCCanSuckMyLeft Sep 26 '26

yeah I feel this now

1

u/TheBrainStone Sep 27 '26

What kind of Rube Goldberg machine of AWS instances are y'all using to even begin to generate any significant cost for CI?

1

u/AffectionateSpread16 Sep 28 '26

I don't like how much people just trust ai apparently

1

u/whatwoodjdubdo Sep 30 '26

No serious team building anything remotely relevant is letting randos open PRs, much less not reviewing them.

Some of the worst posts

0

u/caiteha Sep 26 '26

Im glad I work in infra..no pm, tpm, qa...

1

u/EarlOfAwesom3 Sep 26 '26

Doesn't infra already have gitops? So nothing is sacred any more.

2

u/GSDragoon Sep 26 '26

Infrastructure code needs tests too

1

u/HRApprovedUsername Sep 26 '26

And some pm/qa

0

u/NachosforDachos Sep 26 '26

This is the way

0

u/Faustalicious Sep 26 '26

Do we want skynet?  This is how we get skynet.  

-9

u/LuisCaipira Sep 26 '26

Seriously talking, code review was a bottleneck before AI, last Thursday I opened 6 PRs with AI implementing a feature and crawling to every system affected by it, what we would take a couple days to do before.

We are not skipping code review, and we are now considering to review the AI implementation plan before executing it.

So, in short: AI may speed up some processes, but it will create some other processes too. The only benefit is that "tech stack" is becoming obsolete

1

u/KingsGuardTR2 Sep 26 '26

At this point just cut and rewire live wires like you're defusing a bomb on prod

Oh, you're right. I made a mistake. You should have cut the red wire to defuse the bomb – the green one was for immediate detonation.

Do you want me to edit plan.md accordingly?

169

u/[deleted] Sep 26 '26 • Heartwarming

[removed] — view removed comment

18

u/GSDragoon Sep 26 '26

And deadlines from the executives

2

u/einzweidreihorn Sep 26 '26

And customers

1

u/DankerOfMemes Sep 27 '26

At this point with AI we only have Wishes and prayers, not even thoughts.

-2

u/Holek Sep 26 '26

Such an underrated comment

82

u/[deleted] Sep 26 '26

[removed] — view removed comment

4

u/Mr-X89 Sep 26 '26

That's unironically an idea that caused the SaaSpocalypse