It&#x27;s an utterly brazen lie to say the company didn&#x27;t know about this.<p>Anyone who&#x27;s ever built anything as part of a team - whether the Linux kernel, a space shuttle, or a Lego set - can tell you design decisions like this cannot be secreted into the final product.<p>So let&#x27;s say a software guy decides to make this fix. How do you do that?<p>- You&#x27;ll have a version control system, won&#x27;t you? At the very least someone will see it. There&#x27;s some interesting if statements referencing the speed of the rear wheels, which you can explain at code review.<p>- How do you test it? I doubt your normal office happens to contain the entire running setup of a diesel engine, with nobody around to notice, and nobody needed to tell you about the details. Because you know, an engine test rig wouldn&#x27;t have details, right? You just turn it on yourself, spin the car up to speed and debug, right? And I&#x27;m sure there&#x27;s nothing complicated about gas measurement, even though it tends not to be a part of CS courses.<p>- What do you tell the cluelessly naive good guy engineer about his results? Would he really only test the car under test conditions? Does any engineer with even the slightest grain of curiosity test only the one mode that he&#x27;s supposed to?