Berry said
This book has a real emphases on the object oriented aspect of Java. It explains it very well using an example of a student registration system which is built out throughout the book to enlight the things treated in each chapter.
Tito J. Morales Thome said
"Beginning Java Objects" es un excelente libro que muestra las minucias de los objetos, la manera correcta en que deben de implementarse, la importancia de la encapsulaci?n y de los beneficios que nos proporciona la herencia.
Estupendamente escrito, claridad y sencillez pero sin llegar a banalidades.
La Programaci?n Orientada a Objetos desde el mejor ?ngulo.
GrouchyDave said
I had the first edition of Beginning Java Objects From Concepts to Code sitting on my bookshelf for about 4 years. Meanwhile, I've taken several different Java training courses ranging from beginner to advanced level. I've been part of a development team, and although my role has generally been more of a business subject matter expert, I have also gotten my hands dirty and done some large chunks of coding, debugging, and refactoring other people's code.
So what's my point? Well, although I've gotten by well enough in a pretty intense OO/Java environment, I've always felt like it was exactly that - getting by. I finally took this book off the shelf and worked my way through ALL of it over the last couple of weeks, and it really pulled things together for me in a way that nothing else has done. I've read about half of Eckel's Thinking in Java (a couple of times), and most of Deitel's Java How to Program, among others, and they're really great at what they do, but I wish I had worked through ALL of this book before (or at the same time as) reading those. Even though I already had a good understanding of Java syntax, this book helped me understand more than just the syntax of "System.out.println()".
I've seen a couple of reviewers comment on Jacquie Barker's friendly tone, and I certainly agree with those reviewers. I felt like she was a trusted colleague helping me along, but not talking down at all.
G. Schierholz said
Regarding Brad's comment, the 'one program' is complex enough to give the reader a lot of practice in understanding the relationships between objects, and that seems to me (an out-of-practice former COBOL programmer) to be the biggest hurdle in understanding object-oriented programming. Barker's book gives more help in this area than the other Java books I've read. I read Eckel's Thinking in Java, and got lost by the middle of the book. Once I've finished Barker, I think I'll get a lot more out of Eckel.
Brad said
I got this book from reading the user recomendations here. I just want to warn people this book is about 900 pages long, and the whole book goes into making just one program (a student registration program for a university). If you have the patience to read a book like this, fine, but for me its a little too drawn out, and nothing I saw thumbing through the chapters jumped out as being interesting or trying to make a point. I have read "Head First Java" and recommend that book for someone who is trying to make sense of OOP.
Edit: I want to update this review by saying that I was too rash in critisizing this book. This book does do a good job of explaining how to plan and organize object oriented constructs to address real world problems rather than just a nuts and bolts overview of OO syntax that most other Java books give. This book however is not a "how to program in Java" book. You are going to have to move on to other Java books to become proficient in coding.
Comments