I believe writing a book is a bold move: By submitting the paper, a narrator claims that they have written some text worth of reading for hours by strangers. I think this book somehow lacked the elegance and 'a-ha' effect I was hoping for. It felt synthetic and unambitious - what you'd expect from a "classic engineering book".
Just as being a great programmer won't make you a good teammate, being a Java champion doesn't make a person a great writer either. I am sure the author has extensive tech knowledge, tough reflecting this on text requires something else.
2 stars is a bit harsh, and if the author was just in the same room as I am in now, probably I wouldn't give the book such a low score. But he's not at Küçükyalı, so here comes the two stars.
I think the main issue is, I felt that the author just opened the list of Sonar issues and starting giving examples from them one by one. Although I've taken some notes, I wouldn't think my thinking about Java OR programming techniques are improved as much as I expected them to after reading 350 pages.