Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If someone has access to the source code, there isn't much that can be done for prevention. I suppose reactive measures, such as attaching a hidden GPS tracker like the ones in expensive rental cars, could detect violations.


Code review, trusted build environments and code signing could entirely prevent a single engineer from modifying the code running on the car.


None of those would stop a tech lead or engineering manager


No, but making an example of him would have reduced the incentive to do it again.

Also, removing him from the the tech lead position would have helped prevent further incidents.


Structure as appropriate for the potential for public harm. If necessary, make it required that an executive sign. If you can’t trust your executives then you shouldn’t have projects that can harm the public. They could have killed the Camry driver.


It is more appropriate to say that the Camry driver who was at fault would have caused a fatal accident.


>>None of those would stop a tech lead or engineering manager

Then something else should. Imagine one guy, gone nuts, changing the code on millions of vehicles in one shot.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: