1. Driver code is your friend. Writing it before you code can be a huge help with determining how you want your program to work. Driver code first; program second.
2. Smurf naming condition: redundant naming scheme.
3. Megamoth: maga-monolithic methods; aka ridiculously huge methods.
4. Law of demeter (don’t call a method on a method)
5. Never print to the screen from the class.
6. When defining methods, it’s better to tell an object to do something to itself, rather than try to go around and do something for the object.
Not good code:
if system_monitor.temperature > 100
if temperature > 100
7. I need to get a notebook, because taking notes on my computer is a pain.