• ByteOnBikes@slrpnk.net
    link
    fedilink
    arrow-up
    9
    ·
    1 month ago

    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.

    • Ziglin@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 month ago

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

    • 0x4E4F@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 month ago

      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”.

        • 0x4E4F@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          1 month ago

          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.

            • 0x4E4F@sh.itjust.worksOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              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.