> One day I think there will be true software engineering. When that happens you won't be able to start software projects without certifications, and most people (or programs!) who actually do the coding will be following careful plans and instructions from the engineers who designed the project.
Sounds really bad.
Software can't fall on your head and kill you, not all of it at least.
Different software should require different professionals building it.
And it's usually not about the software but about the management telling the engineers to take shortcuts or whatever (Boeing comes to mind)
You might enjoy this article on the Therac-25 [1]. It's kind of the standard example of how errors in software can wind up harming people. I have written medical device software for about 30 years. In my experience, delivering high quality software for Class B and Class C devices is both challenging and expensive.
Every software developer should know this story, it is a humbling and important lesson. Yes luckily most of can’t ship code that accidentally kills people but we can absolutely empathize with the conditions which led to it happening.
Thank you so much for the link to the postmortem. I will be sharing it and discussing it with my colleagues. We are currently working on the embedded software for an AED.
Sounds really bad.
Software can't fall on your head and kill you, not all of it at least.
Different software should require different professionals building it.
And it's usually not about the software but about the management telling the engineers to take shortcuts or whatever (Boeing comes to mind)