code

Function names should say what they do

Don't add unneeded context

Don't add the class/object names to properties

Functions should do one thing

Use default arguments instead of short circuiting or conditionals

Keep It Simple Stupid (KISS)

A simple solution is better than a complex one.

Single-Responsibility Principle

Every module, class or function in a computer program should have responsibility over a single part of that program's functionality, and it should encapsulate that part

Explicit Dependencies Principle

Methods and classes should explicitly require any collaborating objects they need in order to function correctly

Dependency Inversion Principle

high level modules should not depend on low level modules; both should depend on abstractions.

Hollywood Principle

Write code to respond to external events, such as from an existing framework

Code should work, but does not have to be efficient.