And you believe that, despite experiencing what happens if you speak up?
We shouldn’t simultaneously require people to take heroic responsibility, while also leaving them high and dry if they do.
Look, there are well established procedures in a lot of industries where products are relied on to keep people safe. They all require quite rigorous development and certification processes and sneaking untested alpha quality software through such a process would be actively malicious and quite possibly criminal in and of itself, at least in some industries.
You're in violent agreement with me ;)
By that token, no action could ever apply to a company—including approving, producing, or releasing—since it is a legal entity, a concept, not a physical thing. For all those actions there was a person actually doing it in the name of the company.
It’s perfectly normal to say, for example, “GenericCorp wrote a press-release about their new product”.
If the software is not reliable enough, then don’t use it in a context where it could kill people.
If a construction firm takes an arbitrary design and then tries to build it in a totally different environment and for a different purpose, then the construction firm is liable, not the original designer. It'd be like Boeing taking a child's paper aeroplane design and making a passenger jet out of it and then blaming the child when it inevitably fails.
Of course that's wildly oversimplifying and multiple entities can be at fault at once. My point is that these are normal things considered in regular engineering and manufacturing
Not making an argument. Asking a clarifying question about someone else’s.
> It'd be like Boeing taking a child's paper aeroplane design and making a passenger jet out of it and then blaming the child when it inevitably fails.
Yes exactly. You are using the same example I used to say the same thing. So which part of my message was ridiculous?
If you didn't intend your comment as a criticism, then you phrased it poorly. Do you actually believe that your scenario happens in reality?
And the only reason the commenter I linked to had that response is because its parent comment was slightly careless in its phrasing. Probably just change “write” to “deploy” to capture the intended meaning.
I did not represent or misrepresent anything. I have asked a question to better understand their thinking.
> If you didn't intend your comment as a criticism, then you phrased it poorly.
Quite probably. I will have to meditate on it.
> Do you actually believe that your scenario happens in reality?
With railway bridges? Never. It would ring alarm bells for everyone from the fabricators to the locomotive engineer.
With software? All the time. Someone publishes some open source code, someone else at a corporation bolts the open source code into some application and now the former “toy train bridge” is a loadbearing key-component of something the original developer could never imagine nor plan for.
This is not theoretical. Very often I’m the one doing the bolting.
And to be clear: my opinion is that the liability should fall with whoever integrated the code and certified it to be fit for some safety critical purpose. As an example if you publish leftpad and i put it into a train brake controller it is my job to make sure it is doing the right thing. If the train crashes you as the author of leftpad bear no responsibility but me as the manufacturer of discount train brakes do.
Take a deep breath. Read my message one more time carefully. Notice the question mark at the end of the last sentence. Think about it. If after that you still think I’m trolling you or anyone else I will be here and happy to respond to your further questions.
Then don't write software to be used in things that are literally always critical situations, like cars.
The line should be where a person tells others that they can rely on the software with their lives - as in the integrator for the end product. Even if I was working on the software for self driving, the same thing would apply - if I wrote some alpha level stuff for the internal demonstration and some manager decided "good enough, ship it", they should be liable for that decision. (Because I wouldn't be able to stop them / may have already left by then)