I’ve been shopping for books lately:
Pragmatic Project Automation (just got it can’t tell yet)
Elements of Java Style a lot of the stuff should be self-evident, but it’s nice to have a handy collection of rules. Eclipse does most of that work for me. And some of the rules were news. So I’ve learned something.
Effective Java, I am half through with the book. As with the ‘Elements of … Style’ there is a lot of stuff in the book that I am already adhereing to, in those cases it’s nice to find validation of one’s own practices, but I have also found a lot of things that I am now dying to try and find those places in my code where it can be improved. And: there’s a lot of discussion waiting to happen after I am done with it because I am not going to accept everything just like that because it is in a book. Some things just need to be questioned and if they are validated by discussion all the better. One way or another discussion about programming practices is a good thing for developers. The book is a very nice and easy read … which is a premiere for a “Fachbuch” in my case.