As someone who works in embedded systems, the least important part of my job is writing the code. The most important is making sure the system works as intende

As someone who works in embedded systems, the least important part of my job is writing the code. The most important is making sure the system works as intended. The code is a way to accomplish that. There are other ways to accomplish that, which frequently will include things like changes to the circuit, changes to the mechanical design, changes to specifications, operating requirements, silicon, or how the user interacts with the system in order to make sure it's working correctly. That the code was incorrectly specced was the bug, and there it matters whether it was written by an unpaid intern, a $9 engineer, or a senior engineer who has enough system knowledge to know what the ramifications of the system interacting this way are, or allowing marketing to make it an optional fault light, or permitting only one sensor to be used as its input. While the ultimate failure is a management one, one of the ways that management failed is they clearly didn't get the proper system-level architecture squared away.