My first reading of this book left me dazed and confused; then I read the reviews on Amazon, which were good, and decided to give it another try; with the same result! The book takes you through the design and development process for a Student Registration System while describing various Java language and OOP concepts along the way. It is well written and Ms. Barker knows what she's doing and where she's going but herein lies the problem. As the reader, I felt like a daytripper on a bus tour with Ms. Barker acting as the sight-seeing guide. If you're looking for an example case study and are curious as to how someone else builds an application; this book is for you. If you want to learn Java or you want to learn OOP, start somewhere else. (Jane Griscti - bartender, May 2001)
I had the opposite experience: OOP had me somewhat dazed and confused until I read this book, perhaps because I learned in college through Thompson books (horrible horrible books, all that I've seen, no matter the subject) and the Deitel series (overkill leading to confusion***).
After working on a few projects then reading this book and The Java Programming Language, I can now use UML with some clarity, perform a decent OOA on a project statement, and relate OO concepts directly to Java code. On the JavaRanch rating system I'd have to give it at least 7, maybe 8 horseshoes. Add another extra horseshoe because this book helped repair some of the damage done by the Thompson Learning series.
Added 3/7/2005: *** I've had a chance to review the later chapters in the book, chapters we never got around to covering in school. I've changed my opinion of the Dietel book, and can now see why some folks endorse it. [ March 07, 2005: Message edited by: Jeff Bosch ]
Give a man a fish, he'll eat for one day. Teach a man to fish, he'll drink all your beer.
Cheers, Jeff (SCJP 1.4 all those years ago...)
Nothing? Or something? Like this tiny ad:
a bit of art, as a gift, that will fit in a stocking