Just finished reading it. If you program for a living, or as a serious hobby, and are reasonably good at it, read this book. I’ll accept no excuses if you take programming seriously. Part of its appeal is how easy a read it is, and it’s written in short sections, so you don’t need to allot a large chunk of time for it. You don’t even have to read it from cover to cover.
The authors give a lot of advice on how to improve your programming, and how to be an asset to your organization. They don’t advocate any one methodology or programming language, and they even avoid taking a side in the Emacs vs. vi argument, but rather focus on issues that will be applicable everywhere.
My next book was going to be Peopleware, but, looking through the table of contents and a couple of sections, it’s not holding much appeal to me, now that I’m a programming team of one. I’ll keep it on my list for later, though.
So, instead, I’ve picked out The Design of Everyday Things as my next technical book. It has been on my wish list for quite some time, and I finally found it at the local bookstore.
