- 出版社: O'Reilly Media, Inc, USA (2006年11月24日)
- 丛书名: A Brain Friendly Guide
- 平装: 504页
- 语种： 英语
- ISBN: 0596008678
- 条形码: 0636920008675, 9780596008673
- 商品尺寸: 20.3 x 3.5 x 23.5 cm
- 商品重量: 1.16 Kg
- ASIN: 0596008678
- 用户评分: 分享我的评价
- 第13位 - 图书 > 进口原版书 > Computers & Technology（计算机与科技） > Computer Science（计算机科学） > Software Engineering > Methodology
- 第39位 - 图书 > 进口原版书 > Computers & Technology（计算机与科技） > Computer Science（计算机科学） > Systems Analysis & Design
- 第57位 - 图书 > 进口原版书 > Computers & Technology（计算机与科技） > Computer Science（计算机科学） > Software Engineering > Design Tools & Techniques
Head First Objects-Oriented Analysis and Design: The Best Introduction to Object Orientated Programming (英语) 平装 – 2006年11月24日
Brett McLaughlin has worked in computers since the Logo days (remember the little triangle?). In recent years, he's become one of the most well-known authors and programmers in the Java and XML communities. He's worked for Nextel Communications, implementing complex enterprise systems, at Lutris Technologies, actually writing application servers, and most recently at O'Reilly Media, Inc., where he continues to write and edit books that matter. His most recent book, Java 1.5 Tiger: A Developer's Notebook, is the first book available on the newest version of Java, and his classic Java and XML remains one of the definitive works on using XML technologies in Java.
|5 星 (0%)|
|4 星 (0%)|
|3 星 (0%)|
|2 星 (0%)|
|1 星 (0%)|
The short conclusion is that I think this book, though a bit outdated with java 1.5 or whatever, does get a lot of good points across as far as how to consider design of classes, program layout, and whatever. At the same time, I didn't find it particularly enlightening, like a lot of it just seemed like common sense when it asked me to solve some things, and some things I don't even completely agree with but arguably that's part of the book's ideas it is trying to get across to the reader. It may be too simple for anybody who's done a bit of professional software work (like maybe they'd pick it up on the job or something), but I think it's a constructive book for anybody who maybe can't quite wrap their head around why their code is so spaghetti like or why their objects have serious copy/paste issues or poor reusability/encapsulation or something.
I think i'd recommend it to anybody taking computer science in high school level? but then again i didn't take any CS classes in high school so that may be a reach also.