Make your code suck less #

12. Schedule time to lower technical debt #

11. Favor high cohesion #

10. Favor loosing coupling #

9. Program with intention #

8. Avoid primitive obsession #

7. Prefer clear code over clever code #

6. Apply Zinsser’s principle on writing #

5. Comment why, not what #

4. Avoid long methods – Apply SLAP #

3. Give good meaningful names #

2. Do tactical code reviews #

Never say whats wrong, always say what can be better.

1. Reduce state and state mutation #

Start with methods and the fields (and getters/setters) will fall into place.

Recap #