You can write code that works, without bugs and robuts but it can still be a complete mess. A code that cannot be inherited, extended, verified or understood in a glance is not good code. Futhermore a code that can’t be modified without knowing what is going to break is not good code. Finally code without test is only legacy code. Nevertheless is not only in the code where a brilliant programmer shines. There are tips, tricks and mindsets that make the difference. These books helped me to step forward in my career helping me to be a better developer.
Clean Code: A Handbook of Agile Software Craftsmanship
Robert C. Martin
When we write code we write a story: the story of a feature, of a product, of a business decision. Code should be easy to read, to understand, to maintain and to inherit. This book is a fundamental set of common sense rules and advices that any developer must read before start to mess thing around.
90
Readability
55
Applicability
85
Usefulness
The Pragmatic Programmer: From Journeyman to Master
Andrew Hun
Sometimes we don’t need a large dissertation about SOLID principles, good practices or a detailed comprehensive comparison between programming paradigms. Sometimes we only need an advice, a bulleted point list to follow, a collection of quick tips about what-to-do-to-be-a-better-programmer and nothing more. This is this book: a simple, dead easy plan to improve ourself, do a better job and boost our career.
80
Readability
75
Applicability
25
Usefulness
97 Things Every Programmer Should Know
Kevlin Henney
Do you ever imagined the day to day of the giant of IT? What if a Google engineer could tell a fun fact about his work? Has a unix core developer ever made a BIG mistake? Which advice would you ask to Martin Fowler? Here you have! A quick handy collection of fun, useful and wise stories from the people who made the history of computer science
100
Readability
50
Applicability
75
Usefulness
