Thanks for reading, author here. You are right that this doesn't say much (at least for experience embedded developers). The follow-up points I want to make:

Thanks for reading, author here. You are right that this doesn't say much (at least for experience embedded developers). The follow-up points I want to make: - there is a lot of value for embedded developers to get acquainted with what is going on in the web world. Not only is there a lot out there that's directly applicable to iot, but the tooling is miles ahead of what I encounter in the embedded world, and a lot can just be scaffolded out. - there is a lot that carries over from senior web development to embedded development, and jumping from one to the other is more about "incidental" complexity (learning new tools, learning to read datasheets, learning some abstractions), but a lot of the more holistic thinking carries over. I see a lot of people scared of even opening the source code to a kernel module and I want to show that it's basically the same as glueing some S3 stuff to an SQS queue, both in complexity and in boringness. I have been working with more junior web people, and shown them that I actually prototype my embedded systems in plain javascript, or using tools like XState, just because it's easier. Once they see how my javascript can be ported almost 1:1 to a C state machine on an arduino, big lights go on. (editing: formatting)