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.
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.
Hey I’m not absolving the engineer for not doing basic interference checks but I’m saying it’s also somebody else’s job I’m sure, Cisco’s not a small company.
They probably reused a PCB from another model that used a paperclip hole reset. They duplicated the design, sent it for testing, and came back with “everything is great, but make the reset a push button before you ship it.” Engineering probably said “ok. But it will need to go back for usability testing” and sales said “fuck that, send it”
Or another possibility, after proto and lots of testing: “we need to move test button a couple of cm to the right, away from the corner. No further tests needed”
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.
Yes it is the engineers fault, but even then there should have been multiple people that should have caught such an issue along the way.
As an engineer, I agree.
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.
Probably both, but you’re right, there’s definitely a qa problem here
It’s very strange engineer, if he doesn’t aware of RJ45 connector form-factors.
Hey I’m not absolving the engineer for not doing basic interference checks but I’m saying it’s also somebody else’s job I’m sure, Cisco’s not a small company.
What’s the point of mentioning that it’s someone else job too?
What’s the point of putting it all on the engineer?
They probably reused a PCB from another model that used a paperclip hole reset. They duplicated the design, sent it for testing, and came back with “everything is great, but make the reset a push button before you ship it.” Engineering probably said “ok. But it will need to go back for usability testing” and sales said “fuck that, send it”
Or another possibility, after proto and lots of testing: “we need to move test button a couple of cm to the right, away from the corner. No further tests needed”