Hacker News Reader

Doesn't mean the security or the quality is up to spec however. Most of the defence sector people I've worked with pretty much run on procedural knowledge developed independently rather than using their nut or consulting the rest of the industry.

This whole thing has gone wrong before: https://www.wired.com/1998/07/sunk-by-windows-nt/

View on HN

Your link describes exactly the situation that boatloads of testing and a massive QA process are put in place to avoid. They slapped NT on something quickly and it broke. The result of extensive QA safeguards is that it takes time to roll out code and you get an outdated OS but with a far smaller chance of those sorts of failures.

That only works if you have some level of determinism.

>boatloads of testing

In this case, quite literally so.

> The source of the problem on the Yorktown was that bad data was fed into an application running on one of the 16 computers on the LAN. The data contained a zero where it shouldn't have, and when the software attempted to divide by zero, a buffer overrun occurred – crashing the entire network and causing the ship to lose control of its propulsion system.

Reply on news.ycombinator.com