3 ms·
You are missing my point. The point is that the impact one has writing embedded software is largely defined in the spec. Other than perfectly meeting that spe
by nightski 8y ago
You are missing my point. The point is that the impact one has writing embedded software is largely defined in the spec. Other than perfectly meeting that spec, there is not a lot of room to go above and beyond and create extra value. I'll admit I am not a 30 year veteran in embedded development, but I did spend a few years in the field.
Embedded development is very time consuming because it's generally so critical to get right and keep bugs to an absolute minimum. Which is also why it's important to keep it as simple as possible. This inherently limits how creative one can get.