News for hackers. Stuff that matters.

A comment on We didn't encrypt your password, we hashed it. Parent comment

Re:We didn't encrypt your password, we hashed it by bigiain on Saturday September 05, 2020 @02:12AM (#24381697)
That sound you hear is millions of actual engineers, ones with qualifications/certifications/professional obligations/legal liability (think “civil”, “mechanical”, “electrical”, et al.) all rolling their eyes yet again at the code monkeys who call themselves “Engineers”, yet aren’t prepared to tell their boss that the decisions they’re trying to make, with inadequate training and experience, are dangerous...

Do you think the guy signing off on a bridge or power station design gets pushed around by “product managers” demanding shitty or cheapskate design or construction?

[ Parent | on HN ]
Re:We didn't encrypt your password, we hashed it by alexbanks on Saturday September 05, 2020 @02:20AM (#24381721)
You’re welcome to disagree about calling them software engineers, but I’m not seeing how that is relevant or constructive to the whole point of this post and comment chain?
[ Parent | on HN ]
Re:We didn't encrypt your password, we hashed it by sokoloff on Saturday September 05, 2020 @08:16AM (#24383018)
The point GP is making that civil engineers will not (knowingly) design an unsafe product just because they got something in a specification that led them to do so. They’ll object and refuse.

You were arguing that the specs or decisions made above their pay grade forced the software engineers into a dangerously faulty design which they dutifully created and shipped.

[ Parent | on HN ]
Re:We didn't encrypt your password, we hashed it by wool_gather on Saturday September 05, 2020 @01:31PM (#24385315)
It's a bit circular, though, isn't it? It is in part due to the fact that a mechanical engineer _has_ that legal certification that they have the standing to meaningfully object, and actually be listened to by their PHB.
[ Parent | on HN ]