Ariane Launch failure

[@Snobiker13]

And Arianespace has done the same thing one more time in 2002, with rocket nozzles. "This has worked before, we don't need to test the effects of these small changes, it will work." And it didn't.

[@Saqib_AliRana]

So far I had always thought about the terrible fate the programmers must have met after this blunder but thanks for this detailed explanation. Also now I know the importance of thorough negative testing and code coverage.

[@ibrahimblahblahyapyap]

Excellent video! Thank you and a special thanks for the great level of detail and simplicity.

[@menotworking]

Thanks for the accurate explanation of the failure (or rather, the cascade of failures). The right software in the wrong rocket is the wrong software!

[@hamptonford3066]

Software Fuzzing tools may help with low level errors such as overflows although these may not have existed back then.

[@IanSommerville]

That's true. The concept certainly existed but I suspect that tools were still at a research stage. They would only have helped if they took into account the possibility that the software would be installed in a different hardware environment.

[@audiobooks3623]

There are two things which are endless.

[@RWBHere]

This is the best explanation about what happened that I've heard. Thank-you, Ian.

[@JoshSeeleX]

Thank you for the complete explaination

[@MrAffz92]

Perhaps it would be better to stick to mechanical systems with such things and the software should just extend to apply to displaying and communicating data as opposed to operating the vehicle the software could also be used for performance data and analytics and communicating that to better track mechanical failures.

[@donnibrasko1]

Gonna need an update for today sir!

[@PhrygianPhrog]

Nice explanation, thanks

[@PapaKakaes]

I think they ought take shoot a god damned X1 Cray with a "lense attached to a good transmitter

[@hassanjaved2227]

Thanks :)

[@itsMe-kc2rf]

MSS എഴുതാൻ വന്നവർ ഉണ്ടോ over over.......!!!!!!!!!!

[@ShinobiEngineer]

🤓👍