• Beanerrr@lemmy.world
    link
    fedilink
    arrow-up
    69
    ·
    1 year ago

    Checking for usability is one of the key parts of design iteration, which is done by product engineers. Source: am product engineer

    • Lazycog
      link
      fedilink
      arrow-up
      23
      arrow-down
      1
      ·
      edit-2
      1 year ago

      Former mechanical design engineer checking in as well: can confirm, the engineer’s fault here.

      You don’t just design it just to work, a hobbyist can do that.

      Edit: Not saying I have never made a mistake, everyone makes mistakes. And of course in a proper (especially big) design department someone always cross checks your work, so there must’ve been multiple people to blame. But mistakes happen and that alone is no reason to fire someone.

      In my first job a senior told me that you will experience making an expensive mistake and that it’ll be a good lesson (I did).

      • merc@sh.itjust.works
        link
        fedilink
        arrow-up
        13
        ·
        1 year ago

        Yes, it’s the engineer’s fault. OTOH, it’s QA’s fault for not catching that mistake, and the company’s fault for releasing a product that wasn’t properly tested.

        We’re talking about Cisco here, a company that sells millions of units. The more units you expect to sell, the more extensive your QA procedures need to be. It’s not like this is their first piece of networking gear either. Maybe they’ve never had this specific error before, but surely they’ve had errors caused by people using a variety of different kinds of ethernet cables. I would imagine they have tests where they plug a dozen different kinds of ethernet cables into every new product they make just to ensure that a cable that has given them problems before doesn’t have issues with this new piece of gear.

        When a problem like this is caught by QA people, it’s mostly the engineer’s fault for a design mistake. When these errors are caught in the wild by customers, it’s the company’s fault for a screw-up somewhere in their QA / test / release procedures.

        • dan@upvote.au
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          1 year ago

          a company that sells millions of units.

          Are they still that popular, even today? From what I’ve seen, many enterprise users have moved towards Juniper and Arista, while small business and prosumer have moved towards Unify and Omada.

          • merc@sh.itjust.works
            link
            fedilink
            arrow-up
            7
            ·
            1 year ago

            Cisco’s worth $224b USD, not all of that is hardware, they also have WebEx, ClamAV, and various other things under other brands. Don’t forget that a lot of their hardware is under other brands too, for example they owned Linksys for a while, and currently own Scientific Atlanta. In total, they’ve acquired 243 different companies over the years, so even if something doesn’t say “Cisco” it may be a Cisco product.

          • nxdefiant@startrek.website
            link
            fedilink
            arrow-up
            6
            ·
            1 year ago

            Cisco has a market cap of a quarter trillion, sadly yes, they’re still around.

            I like Juniper gear. Even with their current supply problems I’d probably still try to go all juniper if I had to make a decision.