|
|
|
|
|
|
by aijoe
1026 days ago
|
|
|
This seems inevitable from a software engineering perspective. Automobile software/firmware sounds HARD. There are so many simultaneous, multi-factor processes being controlled, and mostly with firmware, and all the stories coming out of teams responsible for automobile software/firmware indicate that their level of competence is roughly what you would expect if the technical leadership is hired by managers who's background is in the unrelated field of automobiles. I bet that our lives are largely spared at this time only through the competence of the automobile QA discipline. |
|
|
... On top of that, I think there is a bit of a generational gap between firmware engineers. I have worked with several firmware engineers who were artists at optimizing single threaded superloops and miracle workers at squeezing in yet another feature and become tech leads, only to find they have an infinite blank canvas. Some don't actually have the wisdom to not use the new freedom to paint themselves into a corner. A lot of the old projects are trivial now, but dealing with bureaucratic application-level protocols in firmware without getting requires a set of skills and tricks that don't often translate well from what Cloud/App developers are doing.