My type is a dying breed too, the guys who do their best to write robust code and actually trying to consider edge cases, race conditions, properly sized variables and efficient use of cycles, all the things that embedded guys have done as "embedded" evolved from 6800 to Pic, Atmel and then ESP platforms.

Now people seem to have embraced "move fast and break things" but that's the exact opposite to how embedded is supposed to be done. Don't get me wrong there is some great ESP code out there but there's also a shitload of buggy and poorly documented libraries and devices that require far too many power cycles to keep functioning.

In my opinion one power cycle is too many in the embedded world. Your code should not leak memory. We grew up with BYTES of RAM to use, memory leaks were unthinkable!

And don't get me started on the appalling mess that modern engineers can make with functional block inside a PLC, or their seeming lack of knowledge of industrial control standards that have existed since before the PLC.