LLMs are so sychophantic

that they would have articulated the reasoning of the systems engineers who would have been lobbying for better human factors, training, and visibility of the potential problems. If the systems engineers hadn't been downsized that cycle, it's a here today gone tomorrow discipline at many companies.

Frankly, I think the Star Wars trope of humans disrespecting droids was prophetic. We're coming to a world where an LLM will spout off far more about a topic than you want to hear, and your attention just wanders off of them - rudely if they were an organic humanoid - without a further thought, until you want them to talk to the navicomputer or something else that they're suited for.

Never tell me the odds.

There are all kinds of aspects to software development. Under-training pilots and then having software lead them to crash a plane full of passengers counts as a software development fail in my book. Also a human factors fail, marketing fail, a management fail, a quality systems fail, probably a regulatory oversight fail... it's up there with ignoring the guy telling the Space Shuttle mission control not to launch when it has been under 32F the night before, which wasn't a software fail at all, but was a broad cultural failure. Boeing's MAX-10 situation just happened to have software in the crux of the matter.

I do software development. When I see something, I say something. I'm frequently ignored. Several times over the years, I've had the people that ignored me come back asking for help fixing the issue, after they realized that it was more important than they thought it was when they initially ignored me. Luckily, none of the people who died in those situations died (or were harmed in any significant way) because of the problem, but people dying "near the problem" brought the seriousness of it to a level where it finally got addressed.