I like the list. I'd add: * Optimize for readability. * The cost of a bug is exponentially proportional to the time between that it was introduced and the tim

I like the list. I'd add: * Optimize for readability. * The cost of a bug is exponentially proportional to the time between that it was introduced and the time is was discovered (some NIST study): prevent bugs from going to the next phase (requirements -> design -> dev't -> staging -> prod). * Favor FP principles such as: separate data and logic (functions); immutability; explicit nulls; prefer pure functions; etc. Even in non-FP languages. * Strong typing disciplines in languages are worth it.