Challenger blew because the joint was designed to always be in compression--but it went into tension during the twang. After the headlines they paid attention and fixed it.

The Challenger disaster could perfectly well have been avoided if they had been willing to look. There was a clear indication of substantial deviation from design and the joint could have been engineered to stay in compression during the twang.

But Columbia was fundamental. There was an awful lot of insulation aerodynamically before the heat shield. Once again, multiple warnings, but keeping the insulation from being torn off while keeping the weight down was problematic. Columbia was the beginning of the end as they realized they couldn't sweep it under the rug anymore and they couldn't truly fix it.

What we are talking about is the first AI summary page. Simple flag, include it or not. And it's not something that belongs in an educational environment unless you're teaching about the risks of AI. Kids will not have the experience to judge whether it's reasonable to trust it or not.

Unfortunately, the prevalence of scrapers means that anything that could be a scraper is presumed to be so.

Eventually you would expect a lower price, but that's long down the road. In the short run increased demand drives up the price.

They kept jacking up the price but were many years behind on 64-bit. That said to me they were looking to extract cash, not support developers. And C# was just about as good but properly supported. And in time Microsoft closed most of the gaps.

Back in the days of Turbo Pascal you had to know what you were looking at when the memory modified breakpoint went off and you got dumped to the assembly level. And you really had to understand it to deal with the 200mhz bug (there weren't convenient solutions at hand when I first hit it) or when I ended up making extensive modifications to the real mode support in the DPMI mode--never saw that mentioned anywhere. It was nasty--the library was fundamentally flawed and clearly had never actually been used as it declared real mode pointers as "pointer"--which had a very high chance of causing a segment error when the compiler emitted code that copied them by loading them into a segment:offset then storing them. And the debugger was flawed: in single step mode it was emulating, not executing. And the emulation would correctly "execute" an invalid segment register load.

Now, though, in C# I have yet to have any reason to look at assembly.

Back in school it wasn't a problem, people knew "Loren" was male, "Lauren" was female. Now, an awful lot of people don't. It's an uncommon enough name that even if you were around back when that's how it worked you very well might not have known it.

As an adult I routinely get misgendered, but it's a so-what to me.

In borderline cases it can tip the scale to prescribe statin rather than not. But telling you what has happened to your heart doesn't prevent heart attacks.