Translate leasons identified from code audits into common technical practices content

[andrewphilipsmith]

Summary

There are some useful generalisable lessons identified in from previous code audits, which are recorded on this page:
https://alan-turing-institute.github.io/REG-handbook/docs/how_we_work/code_audits/

Impact

It would be more helpful (and discoverable) if these were translated into technical guidance. However, this is not just a case of copy-and-paste into a different page. For example, this identifies a need:

"Installation is a big barrier for software with complex build requirements"

Providing good technical advice (even just pointing to good quality external advice) is non-trivial, but worthwhile.

Alternatives

There is no doubt very good third-party technical advice. This work should prioritise identifying and pointing to third-party technical advice where it exists, and only writing new content where there isn't 3rd party options.

Sections

Updates