- Write meaningful commit messages

- Make systems as observable as possible. Stuff will break, the easier it is to identify the cause, the better. Logging things at different program flow points helps immensely.

- Question every decision in the codebase you are working on, but thoroughly weigh any refactoring attempts

- Don’t fall in love with own code

- Prefer readability over performance (in most cases)

- Don’t follow trends blindly. More than likely your boring stack is the best way to go

- Allow room to recover from a malformed system state

- Don’t abstract prematurely. If you struggle with designing your abstractions, you are probably good with concrete case(s) for now