Six Principles for Building Good Software
These six simple guidelines help our teams write code that never slows down, never crashes unexpectedly, and costs far less to run.
1. Memory First, Disk Last
Fast computer memory (RAM) is thousands of times quicker than reading from a hard drive. If information only needs to be checked and not stored forever, keep it in memory. Erase it cleanly when finished. This makes apps load in less than one second and keeps user data safe.
2. Turn Off Idle Computers
Cloud servers cost money every single second they are switched on. Just as you turn off the light when you leave an empty bedroom, you must turn off cloud servers that are not doing real work. This simple habit saved our company twelve million dollars in a single year.
3. Write Simple Code That a 10-Year-Old Can Understand
Clever code is hard to read and easy to break. The best software builders write clear, simple functions with easy-to-read variable names. If a piece of code is hard to explain, it is usually designed poorly.
4. Small Teams Beat Giant Committees
A focused group of five talented engineers who talk directly to each other will build better software than a 100-person committee bogged down in endless status meetings. Keep teams small, give people clear goals, and let them build.
5. Prove Everything with Honest Numbers
Do not guess how fast your website is running; measure it with a stopwatch. Do not guess how much money a server costs; inspect the invoice line by line. When decisions are grounded in real measurements, mistakes disappear quickly.
6. Respect User Privacy by Default
Do not install sneaky tracking cookies or collect personal phone numbers that you do not need. When software is honest and respects its users, people trust it for decades.