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.
88Checking for usability is one of the key parts of design iteration, which is done by product engineers. Source: am product engineer
68Former 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).
22
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"
24Or 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"
9That seems highly plausible to me
3
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.
15As 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.
6
Probably both, but you're right, there's definitely a qa problem here
9Sounds exactly like something an engineer would say.
4Engineer-adjacent haha
3
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.
83That'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?
65Was usability testing even performed?
If it was, it wasn't tested with every cable type or they would have discovered this issue.
14
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.
16
did they change careers after that? I would want to work on a farm and touch grass every day with my new friends, the animals.
43This is just poor product testing in my opinion. If they just grabbed a bunch of random RJ45’s from the market and plugged them in, they probably would have spotted this. I’m willing to bet this went straight to production.
49The meme is misleading... This particular switch was designed before RJ45 boots were commonplace.
1
/r/crappydesign
Oh wait, this isn't the Reddit anymore.
- !crappydesign@sh.itjust.works
- !assholedesign@lemmy.ml
- !assholedesign@lemmy.world
- !crappydesign@zerobytes.monster
Did I do that right?
30Exclamation mark denotes the community, so:
!crappydesign@zerobytes.monster
The @ is the username indicator, so you've pinged people whose usernames are those for the instance.
16This 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.
3
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.
16Ofc it's Cisco
11that's how you reset a product line
9Was 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.
8I actually, legitimately, laughed out loud at this one 🤣
4Cisco 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.
4Care to elaborate? Sounds like an interesting story.
17Honestly 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.
1Sounds more like arrogant ignorance
0
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
6Surprising opinion, I was only a junior in my brief stint at networking but all my seniors shared this opinion.
2
