4 ms·
Well, it really depends on what the project does. Most general purpose programming has looser requirements (both on specification and implementation) than criti
by aforwardslash 7y ago
Well, it really depends on what the project does. Most general purpose programming has looser requirements (both on specification and implementation) than critical projects. I have the sense you're comparing apples and oranges. Have a look at ex. MISRA https://en.wikipedia.org/wiki/MISRA_C https://en.wikipedia.org/wiki/MISRA_C to have an idea of the strictness applied.
Hint: if you're using any methodology from the "agile" umbrella, it's not even in the same league. Specification and verification processes are arguably the most time-consuming part, not maintaining the code by itself.
- sudoaza 7y agoChecked it, it's nice to have a standard linter, but then even at web development we use those. I know C/C++, embed systems and orbital dynamics will be harder but I would expect them to have the whole mission tested and dry-ran before, at the very least. I'd bet they were just rushed to deliver and focused on a working features checklist instead of thorough testing.
- 0xffff2 7y agoI you think MISRA-C is just "a standard linter" I don't think you've really grasped what it requires. MISRA-C compliant code requires a pretty fundamental shift in thinking.
- sudoaza 7y agoThere are some good common sense recommendations on the general development and then there are basically linter rules. The rules may be more restrictive than others but makes sense for a language such as C and the application is being used. But all this rules can be implemented by a linter and a short checklist. http://caxapa.ru/thumbs/468328/misra-c-2004.pdf http://caxapa.ru/thumbs/468328/misra-c-2004.pdf
- 0xffff2 7y agoAgile has nothing to do with this. I don't want to dox myself, but I currently work on a spacecraft flight software team and we use a lot of agile principles in our development process.