This is a seriously impressive bit of software engineering. It seems as simple as "push a button" to the layman but what happens when: There is a thunderstorm between the airport and the runway The nearest runway is closed due to a blizzard There is a mountain between the normal 3-degree glide-slope and the runway, an "offset approach" There is a 40-knot crosswind You have an engine out That's just a few, I'm a comme…
What kind tech stack/development processes do you think are needed for something like this? At a very naive level, for example: typed language vs dynamic; formal verification of the code or not (or to what extent); what kind of QA? (can't even imagine how to test this "in production" given the amount of edge cases like the ones you describe; hw and sw redundancy; to name a few. I have zero experience with airplane so…
Anyway, I'm sure there used to be a blog for the Dreamliner test team, but I can't find it now, so here's this instead: https://www.wired.com/2010/03/a-look-inside-the-brains-of-bo...
And specifically for code, look here: https://ldra.com/aerospace-defence/standards/misra-cc/
and (JSF, not commercial) https://www.f35.com/about/life-cycle/software