Roberto A. Carrillo Padron said
I'm a software professional and I love this book. It helped me to remember some of the concepts that I have forgotten.
L. Johnson said
Although the books appears easy to understand it it littered with Java code examples so do not buy this book if you aren't comfortable with the Java language.
John Farrar said
The level of design skill needed depends on who you are. This book would not be of much good to a new developer. If you have built a serious program or more in OO then it will make more sense to you. It also makes more sense if you build bigger applications. My suggestion is put the book on your shelf and pick it up every three or four months as you learn OO. When you arrive the book will be a five. If you expect it to turn your software into five before you are familiar enough with project needs you are looking for being part of a magic solution. It takes experience with coding and business before you will grasp how to use these nuggets of gold.
Mostafa farghaly said
It's my first experiment with head fisrt book, and it will not be the last, the book is wonderfull by all meanings of the word, now i can think about big systems implementation easy, now i have a lot of tools under my belt to analyse any system and put it into working software , i learned how to listen to the customer carefully and collect features and write uses case for each scenario and convert my customer words into classes and methods on UML diagram (big picture), and learned how to determine the architecturually siginificant features to begin coding , and learned which method to use : feature driven developement or test driven developement , and how to write test cases and learned alot of OO principles (the best part), when to use inheritance, delegation, interfaces, aggregation and composition and learned Open closed priniciple , liskov substitution principle, single responisibility principle and don't repeat yourself principle for better, extensible and easy to modify code , all that great stuff and more in the book illustrated by funny pictures ( i can't forget the head on a table say to it self: it really sucks to be abstract method. you don't have a body) and programmers discussion and puzzles and dogs barking , really iam proud to read this book , and i canot wait to read Head first networking and i hope it releaed soon .
Mark A. Lucas said
In spite of an otherwise good and 'casual' approach to explaining the concepts of OOA&D, the examples are SILLY and NOT RELATIVE to the business world. Examples of defining classes for dogs and other 'real' world objcets, then trying to relate how the Analysis (ie. Requirements) objects relate to CODE - FALL FLATE and do NOT help explain the connection from analysis to design to working code.
CUTE is nice warm and fuzzy, but does not help someone new to OOAD (and God forbid they are CS grads without Any Real-World experience - esp in business systems!) understand how to perform business-based requirements analysis and transition it into designs and eventually functioning, OO code.... Good and cute but NOT great...
Comments