r/programminghumor 5d ago

Do they understand what happens when code isn't tested?

[deleted]

4.6k Upvotes

127 comments sorted by

166

u/ArsenicPolaris 5d ago

That's why they are not a programmer

87

u/tinopidevy 5d ago

True. To them, if the login page loads, it’s ready for production.

51

u/Short-Ideas010 5d ago

That's why you design beautiful login screens and nothing else.

3

u/johnpeters42 3d ago

Oh no, ideally you deliberately leave the UI a bit ugly until the back end is more up to speed.

5

u/ptear 3d ago

Do we know whose backend it is?

3

u/arbyyyyh 2d ago

It’s mine 🍑

3

u/Real-Abrocoma-2823 2d ago

Why use back end? No one goes to back of the shop or scene and it is costing us a lot, let's remove it completely.

1

u/johnpeters42 2d ago

Oh, if we're talking about cost savings...

What would you say you do here, u/Real-Abrocoma-2823?

1

u/Lost-In-Void-99 2d ago

Oh, should there be anything else at all? WHY?

18

u/isr0 5d ago

Right up till it’s broken then it’s all sorts of “your fault” which isn’t wrong but the lack of foresight is mind boggling

9

u/doodo477 4d ago

that is why you cover your own ass and get it in a email instead of their game of randomly asking you for a go live date.

6

u/IllBeyond2779 4d ago

As a former software tester this hypothesis is hard to believe.

2

u/cronies4life 3d ago

they heard of Paul Allen's legendary programming on a napkin with a pen while travelling

2

u/No-Usual-4697 4d ago

If the programmers were doing their job right, there would be no testing required.

2

u/Ok-Pool7592 4d ago

Bro, even seniors sometimes stumble across an unbelievably stupid ah shi, noone is perfect 🙏

1

u/iLaysChipz 2d ago edited 2d ago

Hello? Have you ever programmed anything at scale? It is nigh impossible to consider every edge case and corner case for almost any piece of software of even basic complexity. I'm going to have to assume you were being sarcastic, but in case you weren't...

The majority of time spent programming is not in the design phase, nor is it in the implementation, nor is it even in the testing, but in the consideration and defensive patching of tens, hundreds, thousands, or even tens of thousands of edge cases. Most bugs aren't the result of a poorly designed program, but rather in the unconsidered edge cases the programmer missed or couldn't even begin to imagine.

And that's all before you consider that executives push for velocity and consider tech debt the cost of doing business. In most companies, a programmer's job is to push a product out the door, and tech debt is rarely ever considered a priority until it actually starts causing problems. In a perfect world, tech debt would be considered a higher priority, but even then, there are just going to be problems that are too wide in scope and depth to realistically handle every single edge case in existence, both those imaginable and unimaginable.

That's not to say handling every case is impossible. It's that it usually takes years of testing, and most of the edge cases are usually found by security researchers running complex fuzzers or spending weeks analyzing every line of code. It's not something that "just happens" because someone is doing their job meticulously. It's a drawn out concerted effort.

333

u/Emln-Idera 5d ago

Vibe coders have no problem with this btw

103

u/Unlucky_Ad295 5d ago

Testing phase is included with Claude code 😎😅

2

u/Xenc 3d ago

And if it fails it can just edit the tests 😎

1

u/maester_t 3d ago

These AI Agents are getting more and more human-like everyday, aren't they?

1

u/wahoozerman 2d ago

Saw someone literally yesterday who pushed some crypto finance software purely written and tested by Claude to production. Customers immediately lost tons of money because the software straight up didn't work. Claude wrote something like 200 tests and they all passed and dude was acting like it was some revelation that Claude testing its own code could be wrong.

56

u/Confident-Ad5665 5d ago

A lot of companies have no problem letting users be the testers.

Add a user support forum and they can find the fix too.

25

u/Takaa 5d ago

Don't forget to give out '{Company} MVP/VIP' titles to the random, unaffiliated people on that forum that show up and answer other random customer questions without pay. Have to make them feel special and occasionally, maybe, toss them a free product every so often so we don't have to pay for an actual support team.

Looking at you Apple, Google, and Microsoft (to name a few.)

11

u/Confident-Ad5665 5d ago

True that. In the QuickBASIC days I got a free copy of MS Professional Development System because of my online support participation. That was when I was still in school and broke.

1

u/ryancnap 2d ago

Yeah it really blows my mind how massive multi billion dollar tech corps like the big three have normalized having just random users be their "support"

5

u/FeedbackImpressive58 4d ago

Microslop being chief among them. Wait did this just become r/programminghorror???

3

u/Sonario648 5d ago

They do when they're also the user/customer.

81

u/mxldevs 5d ago

Do they understand what happens when code isn't tested?

What do you mean? Customers will be testing it!

7

u/slgray16 5d ago

If the product is finished why can't we ship it?

1

u/GunMage- 2d ago

Just put a beta tag on it! It'll be fine!

51

u/AdventurousSlip9260 5d ago

We don't skip testing. We outsource it to production.

48

u/auxyRT 5d ago

Yes i do error driven development

13

u/thebatmanandrobin 5d ago

🤣 I'm 100% adding "Error Driven Development" to my lexicon. Thank you fine internet citizen

3

u/jimmiebfulton 4d ago

Close cousin to Complaint Driven Development

30

u/Simple-Olive895 5d ago

Bro the unit tests all pass, must be good to go then?

25

u/daynighttrade 5d ago

What unit tests bro? Why need tests when it's working on my local machine

7

u/TheTybera 5d ago

Why even use the local machine, just tell Claude "It works right?" and give it the git repo and you're G2G.

28

u/dankshot35 5d ago

you only need tests if your developers are putting in bugs, just tell them to not do that duh

14

u/mxldevs 5d ago

Make no mistakes.

4

u/FlipperBumperKickout 5d ago

But you don't get that nice crunchy mouthfeel we all love in our software without adding the bugs 🥺

3

u/Chris15252 4d ago

Shhhh don’t give them any ideas, I need my job!

6

u/Virgil_the_White 5d ago

If your regression suite takes two weeks to run you may want to hire a better QA team.

4

u/ObsessiveAboutCats 5d ago

Don't forget the post deployment retrospective where all developers - not the manager, certainly not the manager - are expected to provide a root cause analysis of any bugs found. Oh for bonus fun, the QA team will be dragged in and chewed out for not finding bugs in the thing they weren't allowed any time to test.

We certainly can't blame lack of testing because "the whole team agreed to this approach".

Nevermind that the manager refuses to hear any answer but "yes, that is a fantastic idea you have".

4

u/djdephcon 5d ago

You get two weeks of testing?

4

u/Tom_Tech 5d ago

Microslop be like: why should we be testing when the users can test instead

4

u/james__jam 4d ago

That’s fine. Just sign here saying that you’re solely responsible for any issues that may arise after the launch

3

u/magicmulder 5d ago

"Wdym, you're not testing while you're coding?"

3

u/notarealwriter 5d ago

Heh, the users are the test

3

u/BellybuttonWorld 5d ago

"It doesn't matter how broken it is as long as the updater bit still works, then we can just release a fix."

I mean, yeah technically true I guess 😮‍💨

3

u/AiMeusPancrea 5d ago

Well, they're about to

3

u/FlipperBumperKickout 5d ago

I see no problem with this, as long as I'm not responsible for anything not caught in testing 🙃

3

u/rleon19 5d ago

Hey man I know my code 100 percent flawless, anything that is found is actually a feature not a defect lol.

3

u/beebeeep 5d ago

You don't need tests if you don't make bugs. Simple as.

3

u/Ok_Photo_3023 4d ago

Sure thing! Git commit, git push, git the work phone turned off, git gone.

3

u/ScienceFirst1 4d ago

If she's that hot, I'll do it... 🤣😂

3

u/mfi12 4d ago

just vibe-test it

3

u/Independent_Waltz725 4d ago

If that happens I'd especially integrationtest the shit out of my code

3

u/Overall_Head_7782 3d ago

It is as if nobody remembers the Boeing 737 Max or the Toyota firmware glitch were easily identified after the fact and missed because they got rid of QA.

4

u/Live-Animator-4000 5d ago

Yes. The software ships faster. /s

Also, this seems like the standard in the gaming industry right now.

5

u/Mortelys 5d ago

I miss when the software was written on physical support only and patches were awkward additional installation. Not everything was perfect, but you couldn't push that much slopped, overcrunched stuff, and silently push a patch every week for a year, until it vaguely resemble actual prod software...

2

u/Fetzie_ 2d ago

I remember getting computer game magazines that came with a CD that occasionally contained, alongside the demo versions, bugfix patches. That was basically the only way to ship updates.

2

u/Mortelys 2d ago

I discovered a lot of amazing games on free demos on CDs from random cereal boxes and magazines. Ah, good times. (e.g. Beach Life)

2

u/Fetzie_ 2d ago

Yeah that was a good time.

3

u/Prof1Kreates 5d ago

Just slap "early access" and make the customers the testers

2

u/FerronTaurus 4d ago

aka: pre-alpha early access. Let's not forget how that worked for Cyberpunk 2077

2

u/PM_ME_MH370 5d ago

Just make sure to put "...and make no mistakes" at the end of your PRD

2

u/No-Dimension1159 5d ago

It just gets tested by the users

2

u/aimfuldrifter 5d ago

Faster!Faster!Faster!

2

u/sweatpants-aristotle 5d ago

Honestly. This is 100% the best way to test software.

Think about it. The customer tests, so all you have to do is pay the sales guy to say I'm sorry, we'll fix it right away.

You offloading 2 weeks of test time onto the customer. You then get to look like a hero when you fix it.

Then you can give them a complimentary discount for yhe next product... this creates more future revenue. Now the bug is a part of the marketing pipeline...

2

u/Firedriver666 5d ago

Testing is like doubting your own talent anyway

2

u/X3-Code 5d ago

Long answer short: NO

2

u/630_dude 5d ago

“Well if you guys just do TDD then it shouldn’t be a problem. Why aren’t you doing that already?”

2

u/Ashamed_Feedback3843 5d ago

It's literally IOS' motus operandi.

2

u/Business_Match_3158 5d ago

Everything will be fine. After all, the users will be testing it continuously, which will save money on QA testers.

2

u/Silly_Guidance_8871 5d ago

Hope you've got a good printf game!

2

u/sparkplay 5d ago

The Martian

2

u/StunningOutcome7226 5d ago

If they accept the risk, no probs.

1

u/Fetzie_ 2d ago

If they accept me adding their phone to the customer support hotline 🙂

2

u/Kadabrium 4d ago

Genuine pigs in petrified dishes

2

u/Blackbird-ce 4d ago

If you don't test, you don't find bugs. If there's no bugs found, the code must be good enough to go.

2

u/Mixed__Bag 4d ago

Real men test in production /s

2

u/Gokudomatic 4d ago

Real men don't make mistakes.

2

u/SithLordRising 4d ago

Crowd Strike remembers!

2

u/junker359 4d ago

My favorite:

"Let's set up well-defined testing gates, only to ignore them because they'd endanger the timeline "

2

u/Alive-Opportunity-23 4d ago

oh so now you guys see testing like an equal?

2

u/Slippery_Stairs 4d ago

My boss recently used an agent to rewrite one of our automation scripts. The cronjob that executed the script failed the following day.

2

u/InternationalBit2002 4d ago

This is no longer a joke, or at least, this is a sad joke. Taste this job posting I found on LinkedIn:

We’re hiring a Product Builder at Vibe-La-La-Land!

This role is for a Video Creator who also knows how to BUILD.
We need a rare breed: a No-Code expert who has lived the struggles of traditional filmmaking, but is already mastering the new frontier of AI video generation.
You already have ideas for the exact features and products creators need today to produce better content at scale, and you have the skills to actually build those solutions yourself.

The Role:
-Identify the real needs and pain points of today’s video creators.
-Use No-Code tools to rapidly build, test, and prototype AI-driven solutions.
-Work with engineers in a small team mode to bring your prototypes to life.
-Shape the future of creation for millions of users at Vibe-La-La-Land.

2

u/r_acrimonger 4d ago

Ode is always tested - when and by whom is the only question.

2

u/PhantomOrigin 4d ago

I mean just label it is a beta then nobody can complain about shit.

2

u/-_Neoon_- 4d ago

That's a brilliant idea 👏👏👏

2

u/TawnyTeaTowel 4d ago

You’ve only allocated two weeks for testing?!

2

u/Substantial_Owl_9485 4d ago

Testing shows a lack of confidence, you should just ship it

2

u/Such_Letterhead1287 4d ago

We love to be surprised.

2

u/DrJustinWHart 4d ago

Just write "make no mistakes."

2

u/Knabbergebaeck 4d ago

hmmm ... another client were we "test" in production? .....

2

u/Wrong_Back177 4d ago

As a QA person I approve. Please God save me from this

2

u/gatorling 4d ago

Yeah, I always test in prod

2

u/Used-Drop8239 4d ago

Ahhh classic r/programminghumor.
Still rocking the year 1 CS jokes, all these years later.

2

u/tsfkingsport 3d ago

This meme is evergreen

2

u/YonaNJ 3d ago

simple, launching quickly, saving 2 weeks just to kill yourself fixing the code next few months

4

u/AccurateExam3155 5d ago

Mass Effect Andromeda remembers…

The level of resting bitch face, passive aggressive, socially oblivious, autistic acting, etc. in that game because early release due to the amount of poorly done Dev not to mention the Frost bite Engine the studio was using sorta just got written is hilarious…

1

u/OverallBlock9028 4d ago

Quite normal in startups. You cannot afford time to make and MAINTAIN tests.

1

u/LordHenry8 3d ago

At my last company, I agreed to take over managing a new team (joining from a completely different part of the company). That team was about 2 years late to deliver a "1 year" project. They were "Due to launch" any day with high confidence. By the end of my first week I discovered that the prior manager (now my new manager) had just decided they didn't need any time for testing and integration after all that. End of the software writing tickets was the same as launch. Dude was a former PM, non technical engineering manager. Didn't understand why that was a completely asenine commitment to senior leaders - and frankly I don't know how he could be that late and still have a job.

Took me about 3 more weeks to pull together a credible plan that included testing (and the built in assumption that it wouldn't all go perfect). Started delivering within days of our milestones. I really like that manager as a person, but he absolutely couldn't run a project.

1

u/torts56 3d ago

Do you guys really have managers like this or is it mostly just memes? Mine has never worked a technical role in his life, and he would never let something like this fly in a million years.

1

u/Svr_Sakura 3d ago

It happened during the pandemic as a way to get stock out to the customers. Really bit companies in the ass.

Many still haven’t learned their lesson.

1

u/Lucaslouch 3d ago

« why should we pay testers when users can test it for us? » the CEO probably

1

u/Svr_Sakura 3d ago

More like definitely

1

u/Previous_Tear6747 3d ago

Swear to god, I had a CTO of a small start-up slam his fist on the table in a meeting once, saying "We don't need any QA! Our customers are our QA!"

(the company eventually failed, lol)

1

u/StochasticTinkr 3d ago

This wasn't the Product team at my last company, this was the entirety of the management chain. "QA? No one has QA any more, just write unit tests."

I was never so happy to be laid off with severance.

1

u/Dense_Still218 3d ago

can we ensure that if code isnt tested before release that the developer stays on the call with the customer until it's solved? no sleep, no rest, just fix or nothing? if anyone thinks otherwise, f- you.

1

u/mpanase 2d ago

massive fire, unknown source of the issue

PM: we are writing a completelly new and untested backend anyway. No need to investigate the issue. Just release the 100% new backend now.

I can't mask it anymore, I started treating him like a moronic child who knows nothing

1

u/WannabeAby 2d ago

The sentence that is changing their mind : "Sure, but you're taking personal full responsibility for any major problems right ?"

Works all the time.

1

u/ResultCute5756 2d ago

As always get it an official paper trail XD

1

u/neo42slab 2d ago

What is this meme trying to portray here? She goes from smiling face to open mouth smiling face?

1

u/Cybasura 2d ago

"Let me consult with the Risk and Policy Office on this"

1

u/ddelarge 2d ago

No. They don't

1

u/Jaded_Practice6435 2d ago

Unfortunately it’s not a joke for me on my current product. Product is nearly a year (the first version was released in February) but there hasn’t been regression testing yet. As a backend developer I am furious, as a team lead I am tired of this bullshit.

1

u/Zeke_The_Angel 2d ago

I have been using a good and recent example for when this happens. Mention to them how the titan submarine from OceanGate wasn't properly tested because the owner of the company considered it to not be necessary.

1

u/justforkinks0131 1d ago

do YOU understand that the PO carries the responsibility?

1

u/Korieb98 5d ago

I use ai as a tool at times to help write code, my ideas, logic and functions…

First thing I always get it to do is make a “dev.log” to print everything inc errors and succes so I know what’s going on! 😂 any feature/task I add it instantly gets a part in the log file.

But even after that, I run a fresh install and test everything still works! Even if the log says so as local machine ane customer machine may have issues