|
|
|
|
|
by Sirened
1489 days ago
|
|
This might be a dumb question, but what does this even look like in industry? I'm honestly not sure how I could "cheat" my way through my job. I have to design features, argue why they're good/worthwhile tradeoffs, and then implement them. Sure, I can steal features from competitors but I can't lie about their impact or fake implementing them because people will surely notice when the feature ships and simply doesn't work. Like, you can't cheat at design verification of a chip. If the chip ships and doesn't work, your ass is getting canned so fast. |
|
For context, these were a safety-critical systems. A lot of times when something went wrong on a research effort, people can cover their tracks by calling it an "anomaly" and avoid further digging to press forward. But a lot of the "anomalies" can be traced back to avoiding requirements or equivalently lying about test outcomes, most of the time due to schedule pressure or just a simple lack of expertise. And because many safety issues are low probability events, people can get lulled into complacency where this behavior becomes normal since it's still rare for something bad to happen.
Another example further down in the discussion was VW's cheating of emission tests by changing their vehicles operation when it was connected to a test stand.