I've found that there isn't a lot of discussion or research around this subject. Shoutout to engprax, a compliance company, for clearly approaching the issue.

I've found that there isn't a lot of discussion or research around this subject. Shoutout to engprax, a compliance company, for clearly approaching the issue. Is it actually an issue though? Software engineers by design (?) are not capital "P" professionals. There's no certification or board underwriting our work. Software engineering/developers have had the latitude to "move fast" and represent the only "professional" trade that has the ability to "try again" (with a deployment) versus a structural engineer for example. > Dr Junade Ali CEng FIET, the Principal Investigator of the study, said: “Recent developments demonstrate the fundamental importance of software engineers being free to raise the alarm when they become aware of potential wrongdoing; unfortunately our research has highlighted that software engineers are not sufficiently protected when they need to do so. From software engineers facing mass retaliation for speaking up and banned gagging clauses still being used, to ‘industry-standard’ software development metrics not considering the public’s risk appetite; this investigation has highlighted systematic and profound issues with society-wide impact, given how integral computers are to all our lives. With the ubiquitous nature of software in modern society are we at the point were we need certification? The development and certification of "industry-standards"? This theme, balancing innovation with responsibility, is throughout the the Biden Administration's Executive Order on the Safe, Secure, Trustworthy Development and Use of Artificial Intelligence (Order). Who is really responsible though? The developers who wrote the code? Or the executive who ordered the change? There's are plenty of examples of this in recent history. Where engineers/developers released code they knew was harmful/fraudulent but did so anyway under fear of retaliation. > FTX (Nishad Singh) https://www.reuters.com/technology/how-secret-software-change-allowed-ftx-use-client-money-2022-12-13/ https://www.reuters.com/technology/how-secret-software-chang... > Pollen https://blog.pragmaticengineer.com/pollen/#:~:text=Later%2C%20it%20turned%20out%2C%20that%20the%20code%20change%20was%20deliberate.%20The%20BBC%20documentary%20revealed%20evidence%20that%20the%20code%20change%20to%20double%20charge%20was%20made%20on%20Friday%2C%2020%20May%202022%2C%20and%20it%20was%20tested%20to%20work%20correctly.%20The%20code%20was%20then%20executed%20by%20%22a%20senior%20employee%22%20on%20Saturday%2C%2021%20May%202022 https://blog.pragmaticengineer.com/pollen/#:~:text=Later%2C%.... I wonder where this is going to go.