Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code. Transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.
"Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability."
"Why do clean code? Because code will be written once, but read a hundred times."
- Follow standard conventions.
- Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
- Boy scout rule. Leave the campground cleaner than you found it.
- Always find root cause. Always look for the root cause of a problem.
Those articles were written by me 2 years ago, they express my own experience of not writing clean code. Be easy :)
If you want to enjoy your job for life. Please follow those guidelines. ;)