Is that the engineers fault? Or is that the people who are supposed to check for usability after the engineer is done designing the functional aspects? Because it's not usually an engineer's job to do this...
Basic product testing is the foundation of manufacturing, an error like this doesn't get all the way through production and it still be just the engineers fault.
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).
You cannot be a layer of security if your attitude is, "this is someone else's problem".
The swiss cheese model of security is what I go by. Yes, no one is perfect, but that's precisely why every single person needs to actually give a damn. (and why people should be paid enough to care) The more layers of protection from catastrophe, the better.
Giving in because others are involved is literally Bystander Effect-ing your job effectiveness. Only idiots should be OK with, "this is someone else's fault."
No, this is also other peoples' fault, but make no mistake: the engineer is on that list.
Some mistakes make you want the person responsible fired, but some mistakes are SO bad that you actually feel sorry for them instead. This falls into the second category.
That's because a flaw like this is the result of SYSTEMATIC failure, not any one person. Who reviewed these designs? Who was responsible for usability testing? Who reviewed those plans? Was usability testing even performed?
Some places don't fire unless the issue is repeated, client-facing, or willfully dangerous (like assaulting co-workers). The theory is: This is the first time this has happened - we learned from it, the engineer specifically probably learned from it. This won't happen again.
This is one of those double edged sword things with Lemmy, since there's so many places a community can be, they all end up being a little smaller. There's got to be a better solution for that. Maybe when creating a community there should be a way to automatically search a large portion of committed all at once and display it to the user.
This reminds me of Macintosh computers from the late '80s/early '90s. The disk drive had no physical eject button and the power button for the computer was a big knob sticking out right below the disk drive. Coming from the PC world, it took me a couple of days to learn to stop turning off the computer every time I tried to eject the disk.
Cisco and Juniper need to die as entities like 5 years ago. They're single-handedly holding back all of networking from entering the modern era of computing.
Honestly can't elaborate too much as I was only a junior network guy at best and it's been a few years since that. But coming from a world of infrastructure as code and CI/CD deployment strategies, the shit we had to do to manage changes on Cisco and juniper switches was ridiculous. It was like stepping back into the stone age.
You must not work in enterprise IT. Every lower level network engineer says this until they gain more skills and experience with them. Then they realize the full extent of features Cisco and Juniper support that others don't
Was there a recall? I remember them sending out an advisory of the default behavior (and how to disable it), then changing the default behavior in software.