>Or for [buggy] software not to get written in the first place.
FTFY
We place too much trust and rely too much on computer systems these days to have the luxury to write software like we used to.
FTFY
We place too much trust and rely too much on computer systems these days to have the luxury to write software like we used to.
And I'm arguing that not doing so might be a good thing. I shudder to think how we'd be off if other infrastructure disciplines took the same approach we take to develop software.
If you build something that people use in important infrastructure, prepare to be on the hook if it fails.
If this person presented it as a real solution, however, then yes I believe he should be held liable, as much as a lawyer would be for recklessly giving out legal advice.
In either case, The developer who built upon the solution without validating it or verifying its correctness should bear most of the blame, regardless of how the answer was given.