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