Use meaningful and pronounceable variable names

Use searchable names

Code an off-switch

Always plan for a way to switch your work off

Learn in Public

Instead of keeping what you learn to yourself, share it as you go, for accountability, feedback, and networking.

Open–closed principle

Software entities should be open for extension, but closed for modification.

Reduce a problem to its lowest sensible abstraction

Framing a problem in its lowest sensible abstraction helps you understand and develop accurate solutions to a problem.

Documentation should be close to the code

Documentation, in all forms, should be as close as it can be to the code.

Compute properties when possible

One single source of truth

Data should be held in one location, duplicates of that data should be by reference only.

Make the invisible, visible

Make the hidden principles, ideas and behaviors which make up a technology organization understood and explicit