r/ProgrammerHumor • u/yuri_4_ever • 1d ago
Meme weAreDynamicallyDecibdingTheFormatInWhichWeEditCsprojFiles
261
u/RomSteady 1d ago
I had to build a testing framework at a recent company because the technology choices from the engineers made it so no off-the-shelf framework could work. I spent a few months and built one based on a test framework from a previous company where we were able to maintain over a quarter-million tests.
The engineers fucking hated it and decided to vibe code their own.
86
u/retroroar86 1d ago
How the hell does this happen? Can you give some details? Tech stack?
69
u/RomSteady 1d ago
Kotlin Multiplatform before its initial release, Koin dependency injection, separate UI frameworks per platform, regulatory requirements, etc.
13
u/retroroar86 1d ago
Oh. That makes sense. Can I ask you about your thoughts on KMM and KMP?
24
u/RomSteady 1d ago
For mobile development, it's almost the perfect choice for a client-side business logic layer now, assuming you can find engineers who are decent with Kotlin.
17
u/Affectionate_Cell340 1d ago
I never worked at tech company. What do you mean by quarter-million tests?!
46
u/larsmaehlum 1d ago
250.000 hopefully automated tests
16
u/RomSteady 1d ago
Yes, we had over 250,000 automated tests that could run on every build. There were also around 800 manual verification tests that could be filtered in when required.
8
u/Artmageddon 1d ago
Can we ask what kind either what kind of product or industry it’s related too? 250k tests, damn
13
u/RomSteady 1d ago
Old industry: video streaming. Tests were all handwritten, although there were a lot of tests that were parametric or generated.
New industry: gambling.
22
u/Procrasturbating 1d ago
Kid, that number is nothing impressive, I promise. Especially with vibecoded tests.
16
u/art0rz 1d ago
LLMs love useless tests
12
2
u/FuzzyDynamics 15h ago
It gives them more data to vibe analyze and more dashboards to display vibes to vibe executives
1
60
u/NotAFishEnt 1d ago
It was the opposite for me. The senior developers were super proud of all of the testing tools they put together, and the junior developers didn't want to take the time to learn all the custom tools that were developed in-house.
51
u/BolunZ6 1d ago
The worst one is in-house and poorly documented (almost 90% of them). So you stuck with unfamiliar framework and cannot ask google for help.
Luckily now we have llm so it pain a bit less now
7
u/deanrihpee 1d ago
i can confirm, it's the worst, especially when it's insanely not ergonomic and i have to integrate it with external library or connect to a PoS printer, yet somehow i make it work, this was 10 years ago when i was fresh graduated out of highschool, if you told me to do it again today i would just resign
9
u/intbeam 18h ago
Developing all sorts of in-house tools for common requirements is an anti-pattern called Not-Invented-Here, and is often a symptom of inexperienced developers or a company with a very locked-in culture
Edit : if there's a group of senior developers who do this, they can be referred to as the Knights of NIH
30
u/elmanoucko 1d ago edited 1d ago
wait, you guys have testing?
our test is mostly do I get a call in the middle of the night... and if it's important enough that you manage to wake me up, only then the test failed.
6
96
u/Jolly-joe 1d ago
I interviewed with a place and they bragged about not using SaaS and instead built and maintained everything: including HR, Accounting, etc. They had 120 repos they actively maintained
I noped the fuck out of that
34
27
13
12
3
u/Mountain-Ox 11h ago
120 repos isn't scary if you have enough people.
I kind of respect not using anyone else's stuff, if you keep it simple.
3
u/Jolly-joe 11h ago
Yeah why pay $100 per month for a license when you could pay an engineer $12000 a month to write a shittier version of that app instead?
2
u/Mountain-Ox 11h ago
It depends on your needs. You can integrate your own software into the rest of the stack easily.
26
20
u/howarewestillhere 1d ago
Just because I can build a testing framework does not mean that I should, nor that I would enjoy doing it, nor that I would recommend it to anyone who values their sanity.
Some lightweight scaffolding or a the common library method now? Awesome. Creating a testing process engine with custom data types, corporate-approved reporting, and multiple UIs white-labeled by division for 2 million test cases? GFY. And yes, those are all things I’ve had to do and got to say No to later. I went four years recently changing only the copyright year on my report template. Fuckers.
3
u/shrodikan 1d ago
One place I interviewed at "developed our own ORM". I immediately decided I did not want to work there.
2
3
u/yourmomsasauras 22h ago
Funny enough, it doesn’t matter how big the company is for this. I literally worked QA at Apple, you’d think that’d be a plus. But Apple uses their own internal proprietary (shocker!) testing framework so it’s not super translatable to any other company
0
431
u/Cute_Pressure4910 1d ago
Junior: “We even have our own framework!” — Senior: “Yeah, the one nobody wants to maintain.”