News for hackers. Stuff that matters.
Re:The Power of 10: Rules for Developing Safety-Critical Cod... by isityouyesitsme on Wednesday June 28, 2023 @09:25PM (#36515158)
Ever write against AUTOSAR?

Vendors will implement full state machines in the preprocessor. Generated code will include the same header 2 or 3 times, because each time through, the state machine has changed and different code is exposed.

I am not joking.

Re:The Power of 10: Rules for Developing Safety-Critical Cod... by Shawnj2 on Wednesday June 28, 2023 @11:52PM (#36516109)
They are the rules for JPL, where they are sending shit to other planets and have 1 incredibly expensive shot to get the software right on the first try. The software cannot have an unrecoverable error condition and the safety critical portions of the code like that used for landing the spacecraft need to work on the first shot no matter what goes wrong. Even other spacecraft don’t need to have as strict rules but this is a different playing field
Re:The Power of 10: Rules for Developing Safety-Critical Cod... by isityouyesitsme on Thursday June 29, 2023 @06:57AM (#36518806)
Perhaps not everyone knows what AUTOSAR is. https://en.m.wikipedia.org/wiki/AUTOSAR. Think: automotive brake controllers, that type of shit. It is safety critical.

My point isn't that the rules apply universally, it's that something found to be a good practice in a safety critical industry is flagrantly discarded in another, without good reason. Literal state machines in the preprocessor. Metaprogramming in C. But because it is generated code, it is "ok."

Re:The Power of 10: Rules for Developing Safety-Critical Cod... by RealityVoid on Thursday June 29, 2023 @05:11PM (#36526770)
The automotive industry is weird like that. They started doing things a way, got stuck in a groove and now if you push back against it they look at you like you killed their dog.

I should really find a different field, for my mental well being.