▲ 705 ▼ Sometimes, it's backwards (sh.itjust.works) submitted 2 years ago* by 0x4E4F@sh.itjust.works to c/programmer_humor@programming.dev 188 comments fedilink hide all child comments
[–] Ziglin@lemmy.world 2 points 2 years ago (1 child) That sounds extremely lazy. I'd expect more from a dev team. permalink fedilink source parent hideshow 2 child comments replies: [–] 0x4E4F@sh.itjust.works [S] 1 point 2 years ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Ziglin@lemmy.world 1 point 2 years ago (1 child) Couldn't they remotely connect to them? permalink fedilink source parent hideshow 2 child comments replies: [–] 0x4E4F@sh.itjust.works [S] 1 point 2 years 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. permalink fedilink source parent
[–] 0x4E4F@sh.itjust.works [S] 1 point 2 years ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Ziglin@lemmy.world 1 point 2 years ago (1 child) Couldn't they remotely connect to them? permalink fedilink source parent hideshow 2 child comments replies: [–] 0x4E4F@sh.itjust.works [S] 1 point 2 years 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. permalink fedilink source parent
[–] Ziglin@lemmy.world 1 point 2 years ago (1 child) Couldn't they remotely connect to them? permalink fedilink source parent hideshow 2 child comments replies: [–] 0x4E4F@sh.itjust.works [S] 1 point 2 years 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. permalink fedilink source parent
[–] 0x4E4F@sh.itjust.works [S] 1 point 2 years 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. permalink fedilink source parent