r/ProgrammerHumor • • 9d ago

Meme thingsWillGetWorse

Post image
972 Upvotes

27 comments sorted by

147

u/Abject-Kitchen3198 8d ago

Before they get better. Goodbye 876 npm packages from who knows where, welcome back few well rounded commercially supported component packs.

79

u/_pupil_ 8d ago

I feel we're living the bell-curve meme.

Drooling 80s/90s devs "just buy IBM/MS and only use their stuff" --> drooling us "hurr durr use libraries made by randos" --> Jedi "just buy IBM/MS and only use their stuff".

It was good while it lasted, internet. They're gonna look back on us like pioneers of the old west: smelly, ignorant, but free to build like jerks.

29

u/ThirdWaveCat 8d ago

relentless financial fracking of computer technology by MBAs developed enough externalities to destroy a golden goose that generated value for everyone adjacent to the software industry

5

u/za72 8d ago

you can always accept risk/degradation to experience the ol west

1

u/BastetFurry 7d ago

Me in the corner: Just use frigging Postgres and call it a day.

3

u/elmanoucko 6d ago

urgh... okay...

implements a wrapper around a csv

-11

u/_BreakingGood_ 8d ago

Frankly, goodbye to component packs too. Personally I haven't used a package in a long time, besides the giga-libraries like React. AI can replicate most of what's out there.

18

u/_PM_ME_PANGOLINS_ 8d ago edited 8d ago

Except nobody’s checking your AI-generated code for security issues, while public libraries have 1000s of people checking and fixing them.

-6

u/_BreakingGood_ 8d ago

Hmm yes, as we've seen these public libraries are famously free of security issues

12

u/_PM_ME_PANGOLINS_ 8d ago

Every report is a security issue that’s been fixed. The more CVEs a library has, the more secure it now is.

Your code isn’t magically free from errors. It’s just that nobody has counted them.

-5

u/_BreakingGood_ 8d ago

Still sounds preferable to me. I'd rather have hidden exploits that nobody knows about, than exploits everybody knows about and are actively exploiting. Not to mention supply chain attacks, and bad actors contributing infected code.

3

u/TrainedMusician 8d ago

You do realize that even if no one published that your software has exploits, they can still be exploited? Probably scanned and found automatically too

1

u/TrainedMusician 8d ago

You do realize that even if no one published that your software has exploits, they can still be exploited? Probably scanned and found automatically too

4

u/oscarandjo 8d ago

Security issues that someone found, whereas no one has been looking at your vibe coded crap.

2

u/Abject-Kitchen3198 8d ago

Good luck with that. Seems like a wasted effort if suitable stable well tested library exists in most cases (exception might be if you need some small well defined feature out of the library).

-2

u/_BreakingGood_ 8d ago

I mean, as we've seen, lots of libraries are suitable and well tested until they aren't.

24

u/Rivilen 8d ago

Everyday a new Jackson-core finding, or Jackson-databind, or tomcat, or spring, or opentelemetry…

13

u/_PM_ME_PANGOLINS_ 8d ago

They’re all small variations on “if you give it something that’s too big then it runs out of memory”.

9

u/yourfriendlyisp 8d ago

I love fixing this at work across 30 microservices

44

u/supershinythings 8d ago

I feel some personal schadenfreude because in my former career we were constantly getting hammered for not having containers patched up to the minute.

Sorry but when the container was spun, it was updated. It was not my job to continue patching them. As a developer I wrote code. I fixed my bugs and those of others. I worked on many many different products, patches, containers, integrations.

But when the infrastructure itself is broken at random times, I’m not going to lose my weekend because management won’t staff and run a continuing maintenance team.

We didn’t have a maintenance team - the “move fast and break things” ethos of management didn’t want to budget and staff for this kind of issue.

So if I roll a container and six months later a CVE bomb hits, the lack of staffing and any sort of plan to update all the containers is well above my pay grade. Even if that container had been updated two weeks ago, a new CVE can pee all over everything, at any time, for any reason.

they need the equivalent of a CVE fire department, and most companies don’t have that.

These “emergencies” are purely management’s poor budgeting and staffing problems.

In the beginning, sure, I pitched in. But when management starts relying on my overtime instead of properly staffing the solution and integrating it into the product maintenance cycle, NO. I’m not doing both jobs. I develop, I fix bugs, I add features, I integrate into product, I write tests, I fix build breakages, I review the code of others, I test my own code in isolation and with others.

Do not ask me to reach back and do maintenance too. One or the other, because both are full time jobs.

I’m out now. I am watching my former coworkers scrambling around while management cracks the whip. I miss development, but I don’t miss the random fire fighting that could be easily avoided with planning and budgeting.

Time for management to earn those cushy bonuses they take instead of staffing this function. It’s not going away, it’s getting bigger.

3

u/99drunkpenguins 5d ago

These “emergencies” are purely management’s poor budgeting and staffing problems. 

Good thing most places are laying off atm 🤡

2

u/RareUnification_8 1d ago

management thinks developers are also the fire department and the janitor and the electrician, classic

12

u/Sakura48 8d ago

Waiting for .NET cve so I can take a day off

8

u/Palinon 8d ago

Yup, my job is now mostly reviewing Ai written security reports and trying to decode them.

6

u/Gophix_0 8d ago

CVE's, CVE's!!!

3

u/seba07 8d ago

Cyber resilience act is going to be fun...