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

Bugs happen. Fact of being written by fleshy meatballs. What should also have been highlighted is that they clearly had no easy way of finding the specific buggy input in the logs nor simulating it without contacting the manufacturer.


It sounds like a simple functional smoke test throwing random flight plans at the system would have eventually (and probably pretty soon) triggered this. I hope they at least do it now.

This reminds me of: https://danluu.com/wat/


No way or no procedure.




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

Search: