- elegant and efficient
- does one thing well
- can easily be read, and enhanced by a developer other than its original author
- meaningful names
- minimal dependencies
- has unit and acceptance tests
- clean code always looks like it was written by someone who cares
- nothing obvious that you can do to make it better
- no duplication
Kaven Thériault KavenTheriault
KavenTheriault
/ clean_code.md
Last active
August 21, 2018 07:24
— forked from wojteklu/clean_code.md
Summary of 'Clean code' by Robert C. Martin