I finished reading the following book “The Pragmatic Programmer” by Andrew Hunt & David Thomas.
The book was published on October 20 1999, yet 13 years later, this book is still one of the renowned books for developers to read.
It’s a short 300-page book looking like this:
This book is not for people who look for language guidelines, framework information or what tools to use. It does not explain how to build web or desktop applications. It’s not a technical book whatsoever, but it discusses the mindset a pragmatic developer should have or work towards. The Pragmatic Programmer is a collection of ideas, observations, and recommendations for software developers, a philosophy on developing software.
For reason, it’s one of the renowned books for developers, since it’s language agnostic. Whether you write Java, Perl, c#, VB.NET, PHP, and one of those other hundred languages, this book is a great book for you. The book handles some general topics like:
- Don’t repeat yourself
- Changing environments and requirements
- Source control
A few of the awesome tips from this book by which a pragmatic developer should live by:
- Provide options, don’t make lame excuses
- Don’t live with broken windows
- Fix the problem, not the blame
- Don’t assume, prove it
- Configure, don’t integrate
- Always design for concurrency
- Test your software, or your users will (lol)
- Treat english as just another programming language (comments)
One of the things I’m going to remember for the rest of my life: Refactoring is a lesson in pain management. Get over it!
It’s not by coincidence the pragmatic programmer has 186 customer reviews on Amazon. It’s a fast and easy to read book and it might just aswell change the way you think and develop. I have been convinced! What about you ?