There's an anecdote I remember reading somewhere: When an 'embedded systems' engineer was to present a web-based product they were tasked to build, the managers/reviewers were puzzled they couldn't find any bugs. Asked about this, the engineer replied: "I didn't know that was an option".
replyDefinitely a different mindset/toolset is required when it comes to building systems that have to be working autonomously without "quick fixes" from the web.
Yes but I would push back a little on the idea that you simply put yourself in a "mindset of writing bug-free code."
replySimpler code has fewer bugs. Embedded code tends to be simpler and more targeted in its role. Of course, putting yourself in the mindset of writing simpler code is great too - if you have the time to do so, and the problem you are solving is itself sufficiently simple.
Embedded code is also simpler because it has to be. When you are confined to a microcontroller, there isn't room for bloated app frameworks, hundreds of NPM packages, etc.
replyWeb interfaces in embedded systems are very common remote exploit mechanisms, so this anecdote for sure isn't the typical experience.
replyMy gut feeling and expectation is that people will be turning their internet off at night, and at all times. At least for a while until this whole new security situation somehow settles with newly invented automation.
replyMay sound weird, but as author of previous comment noted - a lot of appliances need not be connected ever and still benefit humanity.