Agile Java Development with Spring, Hibernate and Eclipse...

Features

• Cover Type: Paperback with 360 pages
• Published by: Sams
• Edition: 1st Edition May 19, 2006
• Written in: English
• ISBN 10 Number: 0672328968
• ISBN 13 Number: 978-0672328961
• Book Dimensions: 9.2 x 6.9 x 1.3 inches
• Weighs: 1.8 pounds

Reader Reviews
I bought Agile Java Development with Spring, Hibernate and Eclipse just because I buy a lot of books. The idea behind it looked very nice. Spring, Hibernate and Eclipse form a very good development platform. I already knew this much. I had even used all of them, but I can always learn more. The book is, according to the author, based on the development of an example project which is also a very good idea. The problems begin when transforming those ideas into the reality of a book. For starters, the book is poorly written/edited. The author gets ahead of himself a lot. "We'll see more on this later" - he says, and later can be a good eight to ten pages. Section and subsection titles seem to have random importance and chapters are strangely structured, as if you were listening to a presentation where the speaker hadn't bothered to order things. "Now, I will explain this", "Now, I'll do that"... "Oh, and by the way, I hadn't said anything about this other thing. I'll mention it now even if it doesn't fit here". The next *big* problem is the code. The book relies a lot on the code, but instead of inserting the code within context, it just comments a couple of selected lines and you're expected to follow along with the downloaded code on your computer. This is a big turn off for me. I don't usually read books by the computer. Then there's that thing about the author. Don't get me wrong. This is the first I've read from Mr. Hemrajani but I'm sure he's a great developer. But a good book, more so a book like this, should be about Agile Development, about Java, about Spring, Hibernate and Eclipse. Sure, I do like an author who can express and convey his own views and opinions, his experience and know-how. But reading this, there's a feeling that this is all only about how _he_ does this or that. There're too many mentions on "this particular piece I wrote years ago about...", too many self-references and details which ultimately do not seem to be all that relevant. To sum it up: The idea is very good, and you may still get good bits from the book. But it *needs* a very thorough re-write and editing work. Comments (3) | | (Report this)