Juts looking at the list of topics it seems to me these are a collection of argument/discussion starters - certifications are bad (or good), checked vs unchecked exceptions, etc - Java developers have been having these conversations for years and everyone has an opinion. I've read 97 things every programmer and 97 things every architect, hope this book is as good :-)
While some topics are more guidelines-that-it's-a-good-idea-to-follow, I think that assuming this book is full of discussion-starters for your team/organisation is a good idea. In fact, a work book club where people take a subset of topics and report back what they think about them is a good way to start these discussions.
To add to what Trisha said, I can report that 97 Things Every Programmer Should Know has been used as a lunchtime session / book club book in a number of companies. We can hope that 97 Things Every Java Programmer Should Know will enjoy a similar future!
Yup, yup, yup. Tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss