this post was submitted on 28 Sep 2024
697 points (96.3% liked)
Programmer Humor
19564 readers
998 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Could you give an example of something related to hardware that most developers don't know about?
Simple example, our NASes are EMC2. The devs over at the company that does the software say they're garbage, we should change them.
Mind you, these things have been running for 10 years straight 24/7, under load most of the time, and we've only swapped like 2 drives, total... but no, they're garbage ๐คฆ....
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.
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".
That sounds extremely lazy. I'd expect more from a dev team.
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.
Couldn't they remotely connect to them?
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.
If it's publicly accessible it likely has a bunch of vulnerabilities so I too understand that look.