Hacker News Reader

Missing the most important Rule of Thumb. This is an embedded device. It has a _known_ purpose. Every software design decision should be based around this. This clears up any code goes here (ISR/Task), or 'Use this algo'.

Literally the main point of 'Embedded'.

View on HN

Yes and no.

Yes for many embedded microcontrollers.

Not so sure for larger devices with possibly several ECUs and in the field upgrades. All of the sudden the whole thing becomes a tiny data center with several nodes, and the architect needs to value some flexibility over clear cut single purpose.

In automotive, embedded is transformed in this way.

If your device doesn't change the way your customer does business, why bother?

Every truly successful device will be used for purposes you didn't dream of when you first created it.

Reply on news.ycombinator.com