I honestly think that MISRA ends up creating worse code that's less reliable because it forces programmers into contortions to get even simple stuff done. It's

I honestly think that MISRA ends up creating worse code that's less reliable because it forces programmers into contortions to get even simple stuff done. It's like programming with one hand tied behind your back - and a lot of it seems to be for no good reason. I'm thoroughly convinced that MISRA was invented by someone who hates programmers and just wants to see them suffer for no reason. Can't use size_t because it's a variable sized type? Yeah, that's not a win. Can't do early returns to keep code clean and clear? Now we have to do a heap of flags and nesting, resulting in less maintainable code. I'm so grateful to have my code improved this way. Even the experts say that "deviations" are sensible and necessary. So what that really means is you shouldn't ever fully comply with MISRA because it's against common sense. And what does that tell you about companies which require MISRA compliance?