this post was submitted on 28 Sep 2024
690 points (96.1% liked)

Programmer Humor

19623 readers
8 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
690
Sometimes, it's backwards (sh.itjust.works)
submitted 2 months ago* (last edited 2 months ago) by 0x4E4F to c/[email protected]
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 2 months ago (2 children)

Accurate!

Developers are frequently excited by the next hot thing or how some billionaire tech companies operate.

I'm guilty of seeing something that was last updated in 2019 and having a look of disgust.

[–] 0x4E4F 4 points 2 months ago (1 children)

Well, at least you admit it, not everyone does.

I do agree that they're out of date, but that wasn't their point, their software somehow doesn't like the NASes, so they had to look into where the problem was. But, their first thought was "let's tell them they're no good and tell them which ones to buy so we wouldn't have to look at the code".

[–] [email protected] 2 points 2 months ago (1 children)

That sounds extremely lazy. I'd expect more from a dev team.

[–] 0x4E4F 1 points 2 months ago* (last edited 2 months ago) (1 children)

Me too, but apparently, that wasn't the case.

My reasoning was, they'd have to send someone over to do tests and build the project on site, install and test, since we couldn't give any of those NASes to them for them to work on the problem, and they'd rather not do that, since it's a lot more work and it's time consuming.

[–] [email protected] 1 points 1 month ago (1 children)

Couldn't they remotely connect to them?

[–] 0x4E4F 1 points 1 month ago* (last edited 1 month ago)

Yeah, they tried that a few times, the software would glitch and Windows would either BSOD or just freeze (had something to do with how their HASP dongle license communicated with the software and the drivers it used, nothing to do with our issue whatsoever, lol). In the end, they had to come down and debug the issue on a separate rig and install. We just couldn't have those interruptions in production.

[–] [email protected] 1 points 2 months ago

If it's publicly accessible it likely has a bunch of vulnerabilities so I too understand that look.