I like the approach; it reminds me of Towards Zero Defect Programming by Allan Stavely and Dijkstra's idea of deriving programs mechanically from their specifications.
Were LLMs used to produce some of the writing? Not sure how to describe it, but it has a certain recognizable writing style (e.g. "The Problem"/"The Solution", lots of bulleted lists with bolded first words, etc.) Readers might appreciate if AI use is disclosed.
Given they have 30 years of what looks to be safety critical UNIX experience, it’s probably not AI. They might come from rigorous fields like medical device engineering where writing and design are continuously audited for spec and standard conformance
Yeah the AI smelling writing style put me off. If you have 30 years of experience then you should have had ample time to build your own prose and style. I'll pass on this.
> Wanted something that teaches the rigour behind certified systems without requiring a decade of on-the-job learning first.
I've built certified systems (munitions), and the pain of certification is almost always in the process not the coding.
The process is expensive, rigorous and lengthy. It's the process that certifies something good enough to get the stamp for release, not the code design or architecture.
I'm going to go out on a limb and say because rust didn't exist 30 years ago?
Anyhoo... seems interesting. I've been trying to convince Claude to produce a verified JavaCard VM implementation, just for the hell of it, and this probably has a bunch of information to help with that.
Integrated circuits don't "start with C". What does that even mean? C is just an interchangeable language the compiler frontend parses.
A microprocessor starts by executing the machine code at the reset vector. This machine code is generated by an assembler or a compiler backend. It has no idea what programming languages are.
I like the approach; it reminds me of Towards Zero Defect Programming by Allan Stavely and Dijkstra's idea of deriving programs mechanically from their specifications.
Were LLMs used to produce some of the writing? Not sure how to describe it, but it has a certain recognizable writing style (e.g. "The Problem"/"The Solution", lots of bulleted lists with bolded first words, etc.) Readers might appreciate if AI use is disclosed.
It’s definitely AI generated. I suspect much of their portfolio is. See spec.md. Also, the committer’s username is “williamofai”.
Given they have 30 years of what looks to be safety critical UNIX experience, it’s probably not AI. They might come from rigorous fields like medical device engineering where writing and design are continuously audited for spec and standard conformance
Yeah the AI smelling writing style put me off. If you have 30 years of experience then you should have had ample time to build your own prose and style. I'll pass on this.
> Wanted something that teaches the rigour behind certified systems without requiring a decade of on-the-job learning first.
I've built certified systems (munitions), and the pain of certification is almost always in the process not the coding.
The process is expensive, rigorous and lengthy. It's the process that certifies something good enough to get the stamp for release, not the code design or architecture.
Great content and approach, thank you!
I'm going to go out on a limb and say because rust didn't exist 30 years ago?
Anyhoo... seems interesting. I've been trying to convince Claude to produce a verified JavaCard VM implementation, just for the hell of it, and this probably has a bunch of information to help with that.
Ya gotta start somewhere, and just about every IC starts at some point with C.
IC?
Integrated Circuits.
Integrated circuits don't "start with C". What does that even mean? C is just an interchangeable language the compiler frontend parses.
A microprocessor starts by executing the machine code at the reset vector. This machine code is generated by an assembler or a compiler backend. It has no idea what programming languages are.