• jaybone@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    10 months ago

    And marketing, and sales. Tons of people would have pointed this out.

    Some small committee of managers would have come up with some reason to dismiss all of these complaints.

    Also there’s a very simple workaround for this that doesn’t require a full recall.

    And what is going on 4 ports to the right? Seems like a similar problem.

    • grue@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 months ago

      And marketing, and sales. Tons of people would have pointed this out.

      Maybe, but (unlike QA and management) I wouldn’t expect them to notice the problem or hold them responsible for failing to do so.

      • jaybone@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        10 months ago

        Marketing (or “product management” or whatever your org calls them) should be creating the requirement docs which the engineers implement. Sales should be learning and using every aspect of the product. Oh I forgot to mention tech docs/pubs, throw them in there too.

        So yeah, this isn’t just “some engineer” and QA. A ton of people would have fucked up.

    • misophist@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months ago

      And what is going on 4 ports to the right? Seems like a similar problem.

      The mini-USB console port? Yeah, that could be a similar issue, but I’ve never had to use that port while a device is in active production. If I can’t access the device via IP on our management fabric, the device is probably in a broken-enough state that I can probably unplug a cable or two to attach a laptop and troubleshoot.