I've recently transitioned from being an "application developer" (to use the article's terminology) to embedded firmware. The difference between the two is not

I've recently transitioned from being an "application developer" (to use the article's terminology) to embedded firmware. The difference between the two is not as great as the article is trying to make it. Yes, there are specialized skills, but that is true of any platform. Win32 and iOS are as far apart from each other as iOS and embedded. I've worked with several developers with 20+ years embedded experience who wrote horrible, unmaintainable code. However, the article's main tenet I agree with: Higher level abstractions are being pushed for lots of platforms. A great example of this is Google Things [0]. I have my doubts about the quality of product you'll get by asking Android developers to write "firmware" for you hardware product, but it is evidence of the general push. The author seems to accept that these pushes will be immediately successful. I have my doubts. [0] - https://developer.android.com/things/ https://developer.android.com/things/