arclight on Nostr: As part of my pitch for a book on revitalizing legacy scientific code back in 2021, I ...
As part of my pitch for a book on revitalizing legacy scientific code back in 2021, I included a brief outline on risk and harm:
"Scientists and engineers have ethical responsibilities within their disciplines that carry over to the software systems they create.
Ask how the failure, use, or misuse of technical software could cause any of the following:
- Injury and loss of life
- Environmental damage
- Misguided policy and regulation
- Misattributed liability
- Compromised scientific integrity
- Psychological harm
- Cultural loss
- Economic damage
- Loss of reputation, privacy, dignity"
This was specifically aimed at code used in a scientific or engineering analysis context (i.e. not flight controls) but I think most of it applies generally. Is there anything obvious or significant that I'm missing?
#ComputingRisk #WritingLegacyCode
"Scientists and engineers have ethical responsibilities within their disciplines that carry over to the software systems they create.
Ask how the failure, use, or misuse of technical software could cause any of the following:
- Injury and loss of life
- Environmental damage
- Misguided policy and regulation
- Misattributed liability
- Compromised scientific integrity
- Psychological harm
- Cultural loss
- Economic damage
- Loss of reputation, privacy, dignity"
This was specifically aimed at code used in a scientific or engineering analysis context (i.e. not flight controls) but I think most of it applies generally. Is there anything obvious or significant that I'm missing?
#ComputingRisk #WritingLegacyCode