Don't expect too much here. Plain and simple comments on some of the books I've read. Did I say something wrong?
Clean Code
by Robert C. Martin
Must read. Good advice on how to really make your code more readable. I have read it. Applied it to some of my projects. And immediately noticed an improved readability and maintainability of my code. It is like this: You have heard about keeping methods short. Method names meaningful. High cohesion. Low coupling. Well, the book shows you in a very visible way - not abstract descriptions - how to do this properly.
Chad Fowler
by The Passionate Programmer
The second edition of the 'My Job Went To India' book. Another recommended read from the Pragmatic Bookshelf. I personally do not believe too much into all the career business and into business itself. But still, the book is a good read with many interesting little stories. Easy to read. Quick to read. Do it.
Andy Hunt
by Pragmatic Thinking and Learning
Another interesting read from the Pragmatic Bookshelf. I found quite a few interesting ideas in there. (I hate these short entries about books I read where I do not really say anything useful about the book. I guess I hope you consider a book mentioned here enough of a reason to grab a copy and read it.)
Johanna Rothman, Esther Derby
by Behind Closed Doors: Secrets of Great Management
Highly recommended book. Especially if you do not like all that management stuff very much and really only want to understand how to differentiate between good and bad management. Every programmer or other kind of technical/IT person should read these. Then look at management in your context. And you will immediately see what managers know what they are doing. And which do not. Well, of course there is a little more to it than that. But seriously, this book helps a lot in recognizing good management.
Robert L. Glass
by Software Conflict 2.0 and Software Creativity 2.0
Glass updated two of his books. Very interesting read. Especially Software Conflict 2.0.
The Pragmatic Programmer
by Andrew Hunt & Dave Thomas
A must read for every serious developer. That's it! I love this book. It somehow managed to streamline my thinking.. Powerful metaphores. Important techniques. This really is a must have! Recommended read!
Working Effectively with Legacy Code
by Michael C. Feathers
Absolutely a must read! Like Kent Beck's Test Driven Development with code you're about to write, the focus on testing is really important with legacy code, too. But what is legacy code? Don't make the mistake of thinking this is about Cobol code or something.. :) Even though it could be Cobol code, it also covers the code you wrote last week - before you knew how to do it the right way.. Have you read Kent Beck's Test Driven Development? Do you do test driven development? If not, there's something out there which definitly is worth exploring.. Michael Feather's book is really good at giving names to common situations/problems. And showing you how to make legacy code 'testable'. All this is important to have a safe foundation for cleaning up legacy code, or adding features, or fixing bugs.. Good and interesting book! Recommended read!
Test Driven Development
by Kent Beck
Very(!) interesting read. Honestly, I am not really as disciplined as one should be to be able to follow this approach. But I surely see the benefits. I understand - in comparison - the limited benefits of "stupid unit testing" as most people I know (including me) are doing. That is, writing the tests after you coded bullshit :) I wish I could just throw away my current behaviour and go 100% TDD (Test Driven Development). But somehow it is not that easy. I am not sure why.. Anyway, this is important stuff! The Art of Unit Testing :-) So grab a copy and read through it. Recommended read!
by Pete McBreen
What a nice book! I wish I could be one of those craftsmen getting paid five times as much as the rest of the world. Seriously, this is a good book. Also sometimes stretching a topic a bit too long or restating a point a bit too often, this book clearly states what people should realize about software development: It's really like that 1 to 10 factor. You simply cannot expect a guy having a Fucked-Up-Bullshit Licensed Engineer certificate to be a good developer. You need to check the background of the people. Ask about their projects. Ask the customers! Get this feedback. This is much more important than some kind of bullshit certificate or perfect grades in school ;-) This book is for managers, I think. Because as a developer, when reading this book, you just get more angry about the way things are.. :-(
Agile Software Development
by Alistair Cockburn
A difficult book. Not easy to read. Well.. for me.. at least. I think I am reading this book for three months now :-) Still not finished. Hmm.. somehow it is not as "easy" as most other books. Is this bad? I am not sure. I guess it is the topic that makes it so "uneasy" to read. Parts of it, like for example about "Theory Building" are very interesting. Other parts like for example the discussion about how people should be seated are.. well.. I guess they are required. But I found them quite.. boring.. :-) Anyway. Very interesting read here. Agile is the way to go. Check out ${ExternalLink( "", "The Agile Alliance" )}. The Unified Process and stuff like that? Not my kind of thing..
Code Complete (2nd Edition)
by Steve McConnell
Forget about the first edition of the book. Total crap! But this 2nd edition. Well.. a lot like a developer matures on his way, Steve managed to drop all the bullshit subjective advice and wrote a nice 'summarizing' book on a lot of topics. Good read this one! Recommended read!
Rapid Development
by Steve McConnell
Didn't like this book. Maybe because I have a different view on things. A bit a least. And maybe, just maybe, because I don't like Micro$oft too much. It's a bit like this guy's first edition of Code Complete. Too subjective. Not really sound.. well..
Code Reading
by Diomidis Spinellis
More or less for beginners only. If you're a passionate developer, you don't need this book. You already do what you do.. bascially.. :)
Coder To Developer
by Mike Gunderloy
I bought this book after I saw it being mentioned on some web-site. Some blog maybe? Joel maybe? Don't remember.. It's not bad. But it's not really good, either. Far from the importance of The Pragmatic Progammer, or Working Effecively with Legacy Code, or Test Driven Development. And somewhere between the quality of Code Complete Edition 1 and 2. But somehow I liked it. It gave me a different view on some topics. Which I always consider a good thing..
Pragmatic Version Control, Pragmatic Unit Testing
by Andrew Hunt & Dave Thomas
Good books - especially for beginners. Contained a few things I didn't know about (some special CVS features). And all in all nice write-ups of how to get started(!) with version control and unit testing.
Pragmatic Project Automation
by Mike Clark
Personally, I think this is the best (read: most intersting) book of the Pragmatic Starter Series.. How to get started with project automation. Build servers, notification, setting up a project, .. Nice book!
Facts and Fallacies of Sofware Engineering
by Robert L. Glass
I liked this book. Sure, you can always disagree on certain topics. But what does that mean? This book has some interesting stories and a lot of interesting 'facts'. I enjoyed reading this one!
Beyond Software Architecture
by Luke Hohmann
The one thing I remember about this book is 'spikes'. Architectural 'spikes'. For exploring a certain aspect of a system's architecture. Well, this topic had been covered in an Artima interview, too. Maybe that's why I remember it.. :) Anyway, I liked this book. Covered some interesting stuff. Far from the quality of The Pragmatic Programmer or something like that. But then again definitly with different subject/focus and therefore worth a read.
Effective C++ Second Edition
by Scott Meyers
Must read for serious C++ developers. My personal opinion on some advanced C++ features (and probably advanced language features in general): Avoid them as often as possible! :)
Programming Pearls
by Jon Bentley
Interesting read. (That was helpful, right? :)