3 ms·
Wouldn't this create a sort of 'chilling effect' where programmers have to conform to a vague expectation? cf. CoC usage in open source code
by quantumwoke 5y ago
Wouldn't this create a sort of 'chilling effect' where programmers have to conform to a vague expectation? cf. CoC usage in open source code
- salawat 5y agoYes, but it solved a very poignant problem for society. It is illegal to knowingly build an unsafe structure. It is illegal to build something that does not comply with relevant regulations (let's ignore the issue of spotty enforcement for a moment that enabled things like the 737 MAX). Software engineering has no way to to constrain or enforce the upholding of the public interest in not being victims of crappy, malicious, or otherwise unsafe/insecure software. How it'd actually play out, is you'd have Software a PE would sign off on meets "code" (think building code), software that doesn't, and boundaries drawn around functional areas or applications that should only be implemented with software that meets "code". The closest thing we have is some DoD standard I think whose name escapes me at the moment.