Musk requirement principle

Requirements belong to individuals, not teams

Murphy's law

Whatever can go wrong will go wrong. So a solution is better the fewer possibilities there are for something to go wrong.

Use default arguments instead of short circuiting or conditionals

Functions should do one thing

Don't add unneeded context

Don't add the class/object names to properties

Function names should say what they do

Function arguments, ideally use 2 or fewer

Use the same vocabulary for the same type of variable

Avoid Mental Mapping

Avoid using shorter replacement variables that aren't explicit

Use explanatory variables

Create variables to add meaning