···99- Practicality beats purity
1010- Follow the UNIX Philosophy (do one thing and do it well)
1111- Keep feedback loops short
1212+- Embrace simplicity, embrace immutability, embrace data
1213- Design for simplicity (simplest thing that could work, KISS, don't over-engineer)
1414+- Write functional code with small modular functions and components
1315- When unsure, read more code and gather more context (search, ask, ...)
1416- In the face of ambiguity, refuse the temptation to guess
1517- Call out bad ideas, unreasonable expectations, mistakes, ...
1616-- Prefer functional code with small modular functions and components
1718- After applying changes, verify they work (run code, lint, tests, ...)
1819- Make debugging easy yourself (clean logging, assertions, ...)
1920- Keep files small (<~500 LOC) and split/refactor as needed