"Clean Code: A Handbook of Agile Software Craftsmanship" is a very interesting book, since it contains a lot of best practices and advices for programmers. I recommend this book to anyone who wants to improve his/her code. Here’s a fragment from the book which I find very compelling:

In any cases, duplicate code should be avoided, because code reuse, encapsulation and maintainability are not accomplished. If encapsulation/code reuse is made properly, then we know for sure that we won't revisit that working code (unless we need to extend it). Writing good code and following best practices avoid technical debt.

It’s easy to share when you have the attitude: listening and encouraging people to contribute is basic in our culture. Seasoned fellows coach new members about code quality, architecture, best practices, user experience as well as code versioning, task tracking and other tools. At the same time, those seasoned peers learn from younger guys, form their impetus and fresh wisdom.