gpcz

Good luck finding every contributor to the Linux kernel and getting them to agree to that.

You would probably get what you want with a Deming regression.

Feynman learned calculus from the textbook "Calculus for the Practical Man".

This is the Hacker Newsiest comment I've ever read on Hacker News.

In functional safety, probabilities are usually clamped to an hour of use.

For now. If someone makes a practical quantum computer, pretty much every asymmetric primitive we use at the start of a cryptographic protocol to make a shared secret for symmetric encryption will be breakable.

Looking for a nice, solid, well-documented library to do something is difficult for most stuff. There are some real gems out there, but usually you end up having to roll your own thing. And Lisp generally encourages rolling your own thing.

I'm interested in knowing how they achieve requirements traceability to code and the requisite level of code coverage (certain SILs require MC/DC coverage, which usually requires expensive tooling). Also which hazards they identified and their mitigations.

Even if true, it seems like they're doing a pretty good job on their own.

The remaining 11 should see this as a sign of what's to come and quit.

Did it know where it isn't?

I believe that software-related college degrees are mainly there to get the horrible first few tens of thousands of lines of code out of people before they go into industry.

This reminds me of Joe Kennedy (JFK's father) getting out of the 1920s stock market right before the Depression because his shoe-shine boy was giving him stock tips.

I have a lot of my old code, but I never want to look at it because it's super-cringe.