Wait till you see how I appropriate NASA's greatness for my LinkedIn thought-leader post.
(I'm typing the text into Photoshop right now, like a quote, with my name, over an image of me looking like an inspirational keynote speaker, in hopes that my LinkedIn post image will be shared rather than unattributed copypasta.)
It'd be cooler if you were typing it into a prompt to allow genAI to make that slide deck for you. Photoshop is so 1990s old and busted with hand in pocket rent seeking subscription. We'll just ignore the subscription necessary to use genAI as that doesn't serve the purpose of the comment.
When I read the oral history linked in the obit I was surprised how scrappy/startup-y NASA was in the early days. Flying to Cape Canaveral and handing a technician a part you just made without any paperwork would probably not fly nowadays
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.
They are aiming for SIL 2 which to the best of my knowledge requires no MC/DC coverage. MC/DC support in rustc is being worked on, but I would not expect the required features to land before end of 2025 or even mid 2026.
