pull down to refresh

archived

the TLDR is to break apart large problems, factor out security-critical code for closer auditing, and demand tests and documentation.

honestly I could imagine the same advice being circulated a decade ago, between managers who don't write code themselves.