That depends the most on what you work on. Of course there is an abundance of embedded shops that do the kind of development that gets tweeted by @internetofshi

That depends the most on what you work on. Of course there is an abundance of embedded shops that do the kind of development that gets tweeted by @internetofshit On the other hand, things like heavy machinery control systems are usually in somewhere in the middle: the machines themselves are burdened by all kinds of regulations, and the machines can kill a dozen people easily by accident if something goes catastrophically wrong, so it would definitely suck to "move fast and break things". Also, like you mentioned, software updates are few and far between. Then there's medical and aviation and friends, where you have MISRA-C and the like. Very process-y, if you like that. Basically, work on SW for tangible things, and pick your poison regarding how much requirements and process you want. I'd say that on a very broad average, things do get more strict going farther down the stack, if for no other reason than that if the lowest level code does not work reliably, then nothing else usually won't either.