Earlier quoted context omitted.
Doesn't it blow your mind that there are no "standards of engineering" or whatever for software? There's no licensure body for software engineers who build software running your car, and therefore no accountability on a personal level. When an engineer builds a bridge, she has to personally sign off on the bridge, saying it's safe, and is risking not only her professional career, but I think she can also be jailed an…
There are many standards of engineering involving software. - https://en.wikipedia.org/wiki/ISO_26262 - https://en.wikipedia.org/wiki/IEC_62304 - https://en.wikipedia.org/wiki/MISRA_C
There aren't any guarantees that they'll be useful, that they'll match the modern development processes in your language, that they'll fit your problem domain, etc.
Those standards are there primarily to make the publisher a buck--not to represent the codified wisdom of up-to-date practitioners in a field.
Until we've got a truly open-source standard for people to code against, we should stop wringing our hands about these things.