Saturday, September 30, 2006

The Pragmatic Programmer

I just recently picked up a copy of The Pragmatic Programmer: From Journeyman to Master and I must say that the book is awesome. This book has easily become one of the most important books that I have read since I started attending Neumont. If you haven't read this book and you are in software development, do yourself a favor and go buy this book right now. The book directly addresses the problems many developers face early on in their careers.

OK, so now you are wondering whats the big deal, right?

There are many reasons why I think this book is such a big deal. This book is written to help you grow as a developer and as a team member, not to solve a technical problem. This book isn't a solution to that pesky EJB bug you are having, or how the Proxy pattern can help your project. Instead it focuses on the facets of programming and working on a team, from learning how an editor and version control, to documentation, testing automation, and pragmatic teams. These are just a few of the sections in The Pragmatic Programmer, once I read the book again I plan on writing a more in-depth review. In closing, go out and read the book now. It will change your way of thinking drastically.


1 comment:

  1. This is a great tip, it’s like a giant undo button for when, that’s right WHEN you screw up your code. And I know I’ve certainly screwed up more times than I care to recall. But there is great sense in this tip. As then if you find a bug, and you need to trace back when the bug originated, if you use source control, you’ll be able to get a snapshot of the code at any given time. It also makes building projects a whole lot easier too!