4 ms·
To be blunt i would trust an engineer making a system that said there was a security concern in a system over a security engineer. The only time you might want
by namelessoracle 4y ago
To be blunt i would trust an engineer making a system that said there was a security concern in a system over a security engineer.
The only time you might want to listen to a security engineer is when they percieve a problem that the builder doesnt and even then my professional experience with security engineers is way too many are boys who cry wolf and parrot whatever the sweeping tools say.
Phrased another way i would trust an engineer who put up a bridge if they said the bridge had issues over an inspector whose paycheck is very much dependent on not finding issues.
- JohnHaugeland 4y agoThat's not how inspection works
- namelessoracle 4y agoReal life inspection? Correct! Thats why its done that way. Google AI Ethicist "inspection" though....
- mdp2021 4y agoIn real life, it would depend on the individual engineer.
- kbenson 4y ago> To be blunt i would trust an engineer making a system that said there was a security concern in a system over a security engineer. That depends quite a bit on what was being discussed. If it's the engineer's work specifically, and what they did and why, that's one thing. If it's an engineer making claims about specific encryption algorithms that they chose to use or not use in the software they wrote which is contradicted by a security professional, you should probably trust he security professional. This seems to me a case of the latter. A software engineer making claims about things that are not their subject of authority, or at least not what they were hired for, and thus have less reason to be listened to about by their employer.