5 comments about Implementing Lean Software Development: From Concept to Cash (The Addison-Wesley Signature Series).

1. This is excellect book for seasoned software developer. I had trouble with some books on XP pushing process as rigid thing ... here in this book there are reasons behind XP process, knowing them allows one to modify process to fit environment... This is just what I needed - this book was excellent investment of my time and money



2. While the book contains many interesting ideas, it is very tedious reading; an in-depth article could have adequately covered the same material. The book is often fairly repetitious with the same story used to make the same point in multiple places. While the title might lead one to expect a fairly "applied" book ("Implementing" and "concept to cash", the actual purpose is to sell you on the concept of lean software development.
   
   The authors like to bring in real-world examples to help bolster their arguments but frequently get the facts or their interpretation wrong. While the authors need not be experts in areas outside their expertise, one would expect that they would fact-check the basis of some fairly definitive statements; here are some examples: "... 16 is the standard number of missiles in a submarine to this day" (wrong since 1979 when first 24 missile Trident sub was launched); "... in 1985 the value of the yen started its steep fall" (actually the value of the yen rose). Nitpicking?---perhaps, but I find them wrong on areas that I know a little bit about, it makes me wonder how well they are doing when citing knowledge that is unfamiliar to me.
   
   The authors belittle an "efficient expert" (the subject of "Cheaper by the Dozen") for believing there is only one way to efficiently do things. They later turn around and advocate that all developers be subjected to inspections---not inspections of their software but inspections of their desks to insure that they are tidy. They opine that a developer with a messy desk will probably be responsible for messy software; do they feel that a little maid-service will massively reduce software defects? (Why is it that morning people and neat-freaks always so self-righteous?). Sounds pretty "one-way" to me.
   
   The bottom line is that you could probably find a good article in print somewhere that would provide you with most of the content here saving both time and money (sounds like the "lean" way to do things). Still you will get some value for your time and money if you do invest in this book.



3. This book brings some discussions around concepts that comes "in a black box". It's always important to review our concepts. To reinforce then, or to change then.



4. This book explains how to apply the lean manufacturing principles developed by Toyota to Software Development. It focuses on increasing the development speed, since a faster speed results in higher efficiency, lower costs, better value for the customer and also drives higher quality. I strongly recommend it as an introduction to the Agile software development methodologies.



5. Implementing Lean Software Development is an essential resource if you want to understand the value of lean software development. It explains the theory of lean manufacturing and how it applies to software development. It contains practical advice for implementing Lean and anecdotes to help you to understand the value of Lean. This is a great addition to the library of any agile developer or project manager.

5 comments about Dreamweaver CS3 for Windows and Macintosh (Visual QuickStart Guide).

1. This book is a completely useless guide to Dreamweaver. Nothing inside it will help you use Dreamweaver or get you any closer to being able to build a website using this powerful software. Under no circumstances should you ever buy this book.
   
   The problem with the book is that, on one hand, it is not a step-by-step guide to building a webpage using Dreamweaver. You do not learn to build a website, and the examples provided in the book are seemingly random. On the other hand, it is not a useful reference text, either -- each section builds upon what you have allegedly learned from building a non-existent, non-specific webpage using the previous chapter.
   
   For example, the "Positioning Page Content" chapter opens with a sentence that begins with, "Now that you've created boxes on your page...", assuming that the previous chapter clearly tells you how to create CSS boxes. It doesn't. You're left wondering why you bought the book at all, if it simply assumes you've learned the things you bought the book to learn.
   
   The book is full of oversights like this. It's sloppily-written, overpriced, and if anything will confuse and derail any attempt you're making to actually learn how to use Dreamweaver. Do not buy it.



2. I have to agree with the previous "utterly useless" review. This book is terrible. I am a complete novice at website design and Dreamweaver. This book does not teach you anything--it does not give you detailed instruction to the novice nor is it a reference book.
   
   If you are a novice like me you will not learn anything from this book. I will be returning to the book store to look for another book. This book was a total waste of time.
   
   This book is incredibly unorganized. For example, in the chapter on CSS this is what is says:
   
   Chapter 5
   Understanding CSS
   Cascading Style Sheets are all about style, looks, and presentation. CSS properties and rules give you an amazing array of control over foregrounds, backgrounds, colors, fonts, positions, alignments, margins, borders, lists, and other aspects of presentations.
   
   Appendix C contains a list of CSS properties. That list is amazing in its scope, but it can be a little overwhelming as well.
   
   Appendix C!!!! This is the explanation of CSS. This book is pathetic. It gives no conceptual explanation of CSS or practical knowledge of how Dreamweaver utilizes it.
   
   Save your money and buy something else.



3. I've taught myself quite a lot of what I do from self-study books, and have never experienced such a frustrating mess as this book. I dutifully went through 3/4 of the book and know absolutlely nothing more about using CSS with Dreamweaver than I did before.
   
   It skips over basic concepts, rehashes the obvious over and over, and makes huge leaps of faith from chapter to chapter. When you go from Chapter 5 to Chapter 6, you'll wonder what happened to the three chapters that should have been between them.
   
   Additionally, the book boasts of a companion website and the ability to email questions to the authors. Well, their website is completely devoid of content, and they don't respond to email questions.
   
   Don't buy this book. Buy ANYTHING else.



4. This is the fourth book I've owned in the Quickstart series (all relating to Adobe design products or their predecessors) and find it to be an excellent series. Each book has been thorough and well-organized without being wordy. As for the negative reviews about this book: it's worth keeping in mind that no publisher is going to stake its reputation (and bottom line) on an incompetent author. Rather, books (and series) are written with a specific agenda. This book is meant to serve as a concise guide and reference manual and is not a tutorial: if you're looking for step-by-step exercises, look elsewhere.



5. I love these Visual QuickStart Guides. I have them for all the Adobe design software. I don't read them, just dip in and out when I need something. I'm swapping over from Go Live to Dreamweaver and this book is a must have reference because it shows where things are... where the properties are, the CSS details, etc. Love it.

5 comments about Creating Web Pages For Dummies, 8th Edition.

1. This is a great starter book, but once you get your web site designed, then what? I wanted to know more about hosting services and costs, etc. Then found another title on here called "The Complete Web Hosting Kit Pro." This is a complete kit that lets you host your web site on your own PC for free. Comes with everything you need... instructions and software to host your site on your PC at home or at work. I recommend both this book and the web hosting kit.



2. This is a great book for the person just getting started in thinking about putting up a web site.
   
   The basic concept here is to use a fairly minimal amount of HTML, which he teaches you, and then one of the hosting services such as GeoCities, Google or AOL to get your site up and running. All in all, he presents an excellent description of what you need to think about, what technologies you need to understand, and the various tools that are available to assist in the construction of the site.
   
   The intent of this book is to enable to get a site up and running, fairly quickly (He says in a day, I think he is a bit optimistic, plan on a weekend, maybe even a three day weekend.) but only after having thought a lot about the various aspects.
   
   Then in chapter 18 he talks just aenough about things like JavaScript, database connectivity, cascading style sheets and more to let you know that you've barely scratched the surface.
   
   An excellent place to get started.



3. Thanks for the quick responce in the product, received what I needed for less



4. I was hoping for something that would help me get started on building my own site. This book is for someone who just wants any site, and is looking for someone else to do for them.



5. This was my first "for Dummies" book purchase and it will be the last (unfortunately, I also purchased "Web Sites for Dummies" at the same time. A How-To book this not....you get no step-by-step instructions, what you do get is a lot of information that is generally available on the internet with a dose of new-age you can do anything you want if you try.........well, at least the title is right..........only a DUMMY would buy this book.

5 comments about Artificial Intelligence: A Modern Approach (2nd Edition) (Prentice Hall Series in Artificial Intelligence).

1. An author of this book is said to have commented that its writing has made him a millionaire. It is used in over 1000 universities for a simple reason, it is good. The book uses the concept of an agent to unify the formerly fragmented field of AI and to link together concepts as diverse as logic programming and ethics. It is very easy to read and touches every area of modern research interest I can think of. The problems have a nice variety of difficulties (although there are no worked-out solutions in the book) and provide a mix between theory and practice, introducing the careful student to concepts and papers not developed in the main text of the chapter. The bibliography is well laid-out and provides useful depth (one of my current research interests was sparked by reading one of the referenced papers in the 2nd chapter).
   
   My only complaint so far (not having finished the entire book) is that some of the definitions in chapter 17's whirlwind introduction to game theory were a little vague. But, a quick look at some other sources clarified things immensely.
   
   It is rare to find a textbook as interesting and clear as this one. If a professor is requiring that you read it, consider yourself fortunate. If you are thinking of reading it yourself, you also are blessed. Look forward to many pleasant evenings.



2. I am half way through and I like it so far. Frankly I am puzzled by other reviewers complaining about "lack of real code examples", they clearly have not read the book carefully: it comes with tons of sample code (online) written in different languages, publishers/authors simply did not want to waste the precious real estate. The book is nearly a thousand pages already.
   
   Otherwise this is a great CS book. Yes there is some math in it, but don't be scared - there is an appendix with all necessary mathematical background you'll need (and you don't need much). I was surprised to see so much historical references in this book, it teaches you not just about most major branches of AI, but also about how they started and where originated from in a "problem -> solution" form. For instance when they talk about genetic algorithms they actually go ahead and write a comprehensive comparison of analogies between biological evolution, genes and their computer-generated counterparts referencing the original work of Darwin and others.
   
   If you're into AI, applied mathematics or computer science, I have no doubt you'll enjoy this book: it's not too focused on something specific (and something you'd need a PhD to understand) while not too shallow and covers fairly wide spectrum of AI problems, including (!) ethical and philosophical issues like "what happens if we succeed?"
   
   Highly recommended.



3. Pros: Well organized, Description is clear and complete, good for beginners.
   Cons: Examples chosen are not the best, author's attempts at humor are quite lame in most cases.



4. Form your own opinion on this book, don't let the gushing over this book force you into questioning your instincts
   
   I thought I liked this book at first, but I had confused interest in AI with regard for this book.
   
   Sure this was ground breaking. But, currently, it is bloated, full of wordy, unclear descriptions. I particularly dislike the coverage in: ch. 7, 8, 9 (logics + reasoning). ch. 13, 14 (prob, belief nets). Make the search chapters shorter, fewer. We get the idea, no need to spend so much time on it. Make the logic chapters shorter, dig deeper into those subjects if you want to use that much of the readers time. Scrap chapter 13 or write it over again (refer reader to Pearl's or others coverage of probability). It is partially to elementary, stating obvious rules with very simple usages. The rest of it jumps around, with unclear explanations. Chapter 14, skims past ideas, not enough time spent explaining ideas.
   
   I particularly like the detailed references at the end of each chapter.
   
   After glancing at Winston, Nilsson, and Poole books, I am leaning towards Poole, especially since I am more interested in the knowledge rep and reasoning than other areas.



5. Following the accolades in the reviews and having a keen interest in AI (as a physician and computer scientist) - I have dived into this book. It took me more than half a year of stubbornly trying to read and understand it. What a disappointment...
   On one hand, the math is inaccessible, least you have a major in computer sciences / statistics, math - or all of the above. It seems some, if not all of the math "proofs" are unnecessary for the matter at hand. Unless there are some sinister motives behind these superfluous math complications - such as providing professors with ammunition for students testing. But why should someone interested in AI - get bogged down in this? Is it really what the authors had in mind?
   On the other hand there are not enough examples to follow and the examples that are there - are inconsistent and insufficient (for example: the `wumpus' world that is used in the logic chapters, actually succeeds to stir an interest in the reader and then ....it is not followed up in the subsequent chapters such as the one on Bayesian networks)...
   Some easy to grasp principles (such as basic propositional logic) are repeated ad nauseam while some difficult subjects (such as MCMC) are left as puzzling axioms, for us to decipher on our own.
   
   I summarize my disappointment asking myself what I got from this effort that I have invested into this book, absorption and digestion wise, professionally speaking:
   1. Did this book help me better understand the depth and breadth of the AI domain? - No.
   2. Am I able to develop, even conceptually a plan for an AI application / "intelligent agent"? Absolutely not.
   3. Did the book clarify for me the fields of logic, machine learning, reasoning, uncertainty, probability and so on? - No. I am as confused now as I was before embarking on this study project, maybe even more so.
   4. Am I a smarter person, able to read now the multitude of scientific articles out there on the AI subject - after finishing this book? - No.
   
   The only reason I gave it 2 stars instead of the single one it deserves - is because of the historical and bibliographical summaries the authors have nicely detailed at the end of each chapter. I've seen other books recommended in these reviews - and I intend to look into them shortly. CAVEAT EMPTOR (buyer beware) !

1 comments about The Art of Computer Programming, Volume 4, Fascicle 0: Introduction to Combinatorial Algorithms and Boolean Functions.

1. For those interested in combinatorial thinking, ranging from combinatorial card game puzzles to how to count the number of ways to do something, this is a great re-introduction. In this first part of the long-awaited Volume 4, Knuth tells you why he loves combinatorics and computer algorithms, and why it took him so long to publish volume 4.
   
   Hearing it from Knuth, the fascicle basically reassured me in my personal dance with mathematics and algorithmics: there is no problem if you love these things!
   
   I highly recommended this to few friends who were computer science students, and they really liked it. They could not stop reading it during a party at our home!
   
   Disclaimer: This review is based on the preview version that was made available on Knuth's home page. I believe not much is changed, except that some errors should be corrected.

5 comments about Microsoft SQL Server(TM) 2005 Administrator's Pocket Consultant (Pro-Administrator's Pocket Consultant).

1. This book is clearly targeted for the beginners and it is a good reference for them. Also, if you are an experienced SQL 2000 DBA/developer and want to get basic but neccessary information on SQL 2005 administration, this is an excellent book.
   
   This covers most areas well except:
   
   1)Security, user, and schema administration. This book's coverage is very scanty.
   2)Replication: very basic coverage at best and it will not help you understand SQL 2005 replication very much.
   3)Data Mirroring: this part is OK, except it doesn't cover it in details as it needs to.
   4)Log shipping: Maybe half a page dedicated to it.
   5)Clustering: no coverage whatsoever.
   6)T-SQL: almost no coverage except for administrative matters ("alter database/table" etc).
   7)Performance tuning: almost none.



2. Sometimes when I read reviews people have written I wonder if they've actually read the book or simply thumbed through it in a bookstore or did a search of the pages. This is an excellent book and I've found it to be extremely helpful in setting up and configuring SQL Server 2005. This book isn't meant to be an allinone monster book, its a concise, focused book covering the core of SQL Server 2005, particularly for administrators but also extremely helpful for developers who are setting up sql boxes too. If you are developing databases for SQL Server 2005 you'll need a focused development book too especially if you are doing datawarehousing or datamart work or reporting services.
   
   I got more out of this book's 548 pages than books nearly twice as big. The book has T-SQL examples throughout and I've used them for administration. The book has excellent coverage of SQL security, nearly 100 pages of security information covered in Chapter 3 "Managing Security, Access, and Network Configuration" and in Chapter 8 "Managing SQL Server 2005 Security". Excellent coverage of log shipping and database mirroring. The book covers schemas for administration perspectives but not in a database development perspective.
   
   I used this book to gain a solid understanding of SQL Server 2005 setup, configuration and management. I refer to it all the time.
   
   This is a great book for your everyday needs and I use it all the time. Highly recommended.



3. SQL Server 2005 Administrator's Pocket Consultant is an excellent reference for DBAs and System Administrators planning to implement and maintain SQL Server 2005. While the book is written for Administrators, database developers will benefit from it as well. This one does a great job of laying it out in plain English. The focus is on daily administration tasks, and there's a heaping helping of SQL commands as well. Highly recommended.



4. This handy pocket consultant is a must have for administrators and developers. It delivers exactly what is promised: a handy guide for daily administration. Out of all my sql server books this is the one I refer to the most.



5. It clearly defies the title but does provide with very useful information. I am quite impressed. I have read this book as a pro. And is recommended only for pros.
   Beginners please read something else first before you jump on this one.

2 comments about Professional LINQ (Programmer to Programmer).

1. Unless you really read between the lines this book has few pages devoted to VB. There is a small chapter on VB and XML with LINQ. I can't even understand why it was even put in here since the rest of the book is C#.
   
   If you are looking for a LINQ to SQL book on VB don't get this.



2. Before proceeding, I have an admission to make. I have worked with Scott as his technical editor on another book. However my assessment here is as objective as I can be.
   
   I have worked with LINQ for quite a while now, since I came across it in the early stages at the MVP summit a few years ago. In many ways I think it's a very easy subject to learn b/c in many ways, it is so similar to SQL. At the same time, as with anything, true mastery is not easy. Because I also teach a course on LINQ and Entity Framework, I buy every LINQ book that I can find and have seen it covered as a topic in many of the most recent C# books. The whole line of LINQ books that have come out are, in my opinion, very good. And while they all cover essentially the same topics, they all have their own way to approach the subject so I've gained a good bit by examining how each author approaches the subject. I think this book is a solid 4.5 stars - there wasn't 4.5 available but I think it's a lot closer to a five than a 4.
   
   Why do I think that? First off, it's thorough. Apparently another reader doesn't agree with this assesment and decided the book warranted 1 star b/c of it's light treatment [..]. While equality and non-discrimination are laudable objectives, I think getting upset b/c a book didn't give equal coverage to both languages is ridiculous and punishing an author with a 1 star review is really unfairly punitive. But, if equal coverage of both languages is what you need in a book - then be advised, you're going to be disappointed. If on the other hand, you feel that you can code in either language and that understanding the framework is what's important, well, you'll find this book rewarding. Code examples in both languages (and hey, if we're going to knock authors for discriminating against VB.NET, why not trash everyone that doesn't cover managed C++ or J# too. And what about F#?) take up a lot of space and Scott uses that space to delve into the functional areas of LINQ.
   
   It starts out covering the new language features of VB.NET 9 and C# 3.0 - features necessary to support linq and which are used commonly when coding with LINQ. Those include features such as object initializers, collection initializers, extension methods, implicitly typed local variables, lambda expressions, expression trees etc.
   
   He proceeds to the basic mechanics of LINQ queries. Much of this is covered in MSDN but he certainly expounds upon each area enough to make a substantive difference in your understanding. He moves on to LINQ to Objects and has a pretty detailed coverage of using LINQ to create business objects. He then moves to LINQ to XML and LINQ to Sql. The LINQ to XML coverage is excellent and leaves you wanting for nothing. The LINQ to Sql discussion is also pretty detailed although the coverage related to passing LINQ through tiers is a little short. However that's the case with each LINQ book and that's mainly b/c LINQ 2 Sql's n-tier story is not a happy one. He does cover the .Attach method which is about all you really can cover in that respect without really covering it as its own topic.
   
   In his coverage of each of these, he covers the use of Lambda expressions and expression trees and provides many examples of each. Readers will likely find this coverage alone justification for buying the book. In my experinece, truly understanding LAMDAS is not hard, but learning them (at least for me) wasn't very linear. Instead of learning a little more each time I studied them, i typically made little progress and then had an 'a-ha' moment. To that end, seeing diverse examples really helped me out along the way - since seeing different implementation helped me have more a-ha's.
   
   With respect to LINQ to Sql - Scott dedicates a good bit of the book to it. In fact, I think he may have dedicated a little too much to it. Not in the sense that other areas were left short b/c he covered L2S so in depth, but I have found that LINQ to sql is very limiting in many business respects and its use in a mulit-tier scenario (and for that matter, any time you can't keep a persistent connection open) really limits its usefulness. He covers the ins and outs of it and has a pretty decent demo application that's built throughout the chapter. THe coverage is extensive enough that you may walk away from it feeling like it'd be a great choice for your own business application - at least in my experience, I've found that may not be the best idea. Again though, it's not the author's fault there are those limitations and it'd be unfair to fault him for covering it too well.
   
   THe book is big enough that he gives each area the attention it deserves so even though Linq 2 sql gets a lot of coverage, so does everythign else. There are copious examples throughout the book and they are all original enough that you can definitely get a full understanding of the issue at hand.
   
   So if you're looking for a solid LINQ reference that covers all of the important aspects of LINQ - you'll like this book. If on the other hand, you are looking for a book that is absolutely non-discriminatory in its coverage of VB.NET (I'll note as well that at no time does this book present itself as though it covered each language equally) - well, learning LINQ is the last of your problems

5 comments about SolidWorks 2007 Bible.

1. By far, this has to be the best SolidWorks book out there. Believe me; I am a Mechanical Engineer and a seasoned SolidWorks user. I have purchased several other instructional books on SolidWorks and very few delivered the information in a well structured manner. Lombard's book is well written and very well organized. The book is written both for the beginner and those who have been using SolidWorks for a while. Everybody can learn from Lombard's book. Bottom line is this: If Lombard was to write another book for SolidWorks 2008, I would definitely buy it.



2. This book has pictures that create the illusion that you are going to learn all of that model and at the end it doesn't show you the way step by step to make those models.



3. I haven't received the SolidWorks Bible yet, thouhg I have it ordered one month ago.
   I am still waiting my book



4. I found it very useful for filling in holes I had with Solid works primarily design tables and some basic programming. It is useful but not terribly detailed. It covers a lot and not much of that a lot in detail.



5. The description of the book states: "The most complete resource for SolidWorks on the market. Matt Lombard's in-depth knowledge plus his snappy wit and wisdom make SolidWorks accessible to users at all levels."
   
   Sheer size with bad wit does not make a book good. It shows for this book!
   
   The book is fragmented, poorly explained, written, and illustrated, with a mound of tips that look like they came from various SW User groups.
   
   As a new 3D CAD user and a Mechanical Engineer with 10+ years in industry, it did not help, nor would it help if I was not a new user.
   
   The book was not recommended by my local SW VAR, I know now and I should have listened!!!!

5 comments about Programming Python.

1. The earlier edition of this book was already 1,300 pages; this one is 300 pages longer. It is by far the largest programming book I've ever owned. (Thankfully my company bought it for me.) It aims for comprehensiveness -- everything you could possibly want to know about Python. Comprehensiveness is not a virtue. When you want to learn English, and your reader already knows all the parts of speech, you don't hand him a dictionary and send him on his way. Comprehensiveness in a programming book is what the author does when he doesn't want to take the time to teach.
   
   What I want to know, when I come to a new language, is how to solve common programming problems in a) the best way possible, using b) the language's native idioms. "Programming Python" absolutely strikes out on a). It doesn't even mention Twisted Python in the index, and only mentions Zope in the context of a web CMS -- even though Zope's generic interface library is used all over the place. As for b), it's hard to tell what the idioms in Python are when they're buried in hundreds of pages of unnecessary verbiage.
   
   If you're an experienced programmer, your ordinary path will be to peruse a book like this, find some code snippets, learn some idioms, then start writing your own. From there, you're likely to turn to web documentation. So in this case, you need a book that's maybe a couple hundred pages long. If, on the other hand, you're a new programmer, you won't start with "Programming Python"; at most you'll start with "Learning Python." So whom does "Programming Python"'s bulk serve?
   
   I've grown sour on programming books, the vast majority of which just do not know their audiences and suffer from atrocious pedagogy. "Programming Python" is one such book.



2. This is my second-favorite Python book, coming in a close second behind Python in a Nutshell. Programming Python does a nice job of covering the "how" of Python, and an even better job of covering the "why" of Python. Some may give this the semi-pejorative label "advocacy," but I'd say it's acceptable when you're preaching to the converted (i.e. purchasers of Python books), and remember also that this book dates back to a time when Python advocacy was actually needed.
   
   Reading this book taught me a lot about how to write "pythonic" code -- code that not only works, but is idiomatic and follows the best practices for Python (and software engineering in general).
   
   Another great thing about this book is that it's also actually enjoyable to read. I found myself reading this one cover to cover, rather than getting in and out as quickly as possible, which is the norm with most of the programming-language references I own.



3. Programming Python by Mark Lutz was surprisingly high level. Unlike the other O'Reilly "Programming ...." books (like Programming Perl) it gives only complex examples. The reader is assumed to have considerable experience with Python to begin with. In that perspective, it is an excellent book, but it will disappoint the newcomer who expects something starting from the from ground up.



4. I bought this book a few years ago, and I think I have finally given up getting anything of use out of it. It has been with me through my entire Python learning experience, so you might think there would be a point at which I would have found it useful, even if that may not presently be the case. Unfortunately, I can say that this is easily the least useful Python book I own. In fact, out of the 6 or so Python books I own, it is the only one I wouldn't miss a bit.
   
   It's just that it never seems to have anything even close to relevant for me, when I'm working on something. I can remember several times where I thought to myself, "What's a good way to solve this problem in Python?", or, "Where can I get some background on why Python does things this way?". Invariably I have either found the answer in one of my other Python books, or on the web. It's not that I haven't tried to like the book, in fact each time a problem comes up, I think "well ok if the book can shed some light on this for me, I'll consider it a value", and yet after 3 years... nothing.
   
   Anyway, I don't want to be all negativity, so to anybody reading this, here are the other Python books I have gotten more value out of:
   
   The Quick Python Book by Harms/McDonald (Old, and yet, still really valuable beginning book)
   Python Essential Reference by Beazley (A great reference book)
   Python Cookbook by Martelli et al (what Programming Python seems like it wants to be, but in half the size and twice the value)
   Python Standard Library (I don't use this much, but it still has some value)
   Python in a Nutshell (I think that's the name, it's at work right now. Another decent reference)
   
   Finally, it pretty much goes without saying, but I'll say it anyway. This is just my experience. I am sure this book has been right on the money for other readers, and that's great, but for me, I think I may be donating this behemoth to my local library soon.



5. One thing I really wish O'Reilly would have made clear on the cover is the version of Python which was current at the time of publication. In this case, it's 2.4, so if you're looking for information on things like function decorators or the new generator abilities that 2.5 brought along, you're going to be as disappointed as I was.
   
   Aside from the fact that some of the information is dated, it's still a good overview of practical solutions to realistic problems which can be solved in the language. It does tend to spend way too much time developing TkInter GUIs (which I do not personally care about one bit) and overusing the usual array of extremely unfunny Monty Python references (which I personally stopped caring about around 1984). If you cut out both of these things the book would probably require about half as much paper per copy, and it'd be a good deal more digestible to boot. There's also lots of Windows-specific silliness and the author continues to operate under the assumption that OS X does not exist (every mention of the Mac platform refers to information that hasn't been accurate for nearly 10 years at this point).

4 comments about Apple Pro Training Series: Color (Apple Pro Training).

1. I ordered this in June of last year and I wish I'd not. I'm a live tv camera shader so my background is in color manipulation. If you have absolutely no idea how to manipulate colorimetry, this is not the book for you at all. It tells you how to drive the software with some helpful color hints scattered about. Read the manual, work in the application, scour the net and Amazon for information about color and you can learn the same stuff.
   
   If you have a background in color manipulation, skip this book and read the manual to learn how to drive Apple's Color. If you're like me and enjoy constant learning, run and pick up "Encyclopedia of Color Correction" by Alexis van Hurkman. It's a far more useful text than this title.



2. Aside from the frustrations of the "one-star-reviewer", one must consider that the purpose of this book is to teach how to use the software. Apple is making professional tools available to the "general public", and is offering a training series of which this book is a part.
   
   One assumes that if you're an industry professional, you're well on your way, without the need for "training wheels". But if you're like me, more or less still exploring the richness and the depth of Final Cut Studio 2, then this book is a must for you.
   
   I was a bit frustrated about the long waiting period and the delay of the publishing date and was close to cancelling my order, but I am happy I own this book now. The book may seem a bit meager and I wish for more examples and exercises in an updated version, but I feel it gives me a great headstart in learning how to use Color and I feel confident enough to explore all the possibilities on my own.



3. I waited a long time before this book arrived but it was completely worth it. I edit on Final cut pro but never really did too much with respect to secondary coloring. I used the color correction tools with Final cut but they are not very good for precision coloring. I've always peeped through the window admiring da vinci system and even considered buying Final Touch but didn't have the nerve to pluck down $20K. Then Apple bought the company and folded it into Final Cut suite. I upgraded immediately. I soon found that i was out of my element in Apple Color.
   The manual that came with Apple color didn't help that much either. Yes i could color but didn't always get the exact look i was going for. I concluded that only Da vinci system could give me the look i wanted.
   Then came this book. It thoroughly explained the right way to mix and match to get precise looks, from skin tone to mood.
   This book is worth twice it's price. Forget going on any silly course. read it and practice and you are good.
   
   I'll say this for Apple color. It can color as good as any da vinci system. It is 10 times slower to render unless you create a huge cluster, granted, but the end result is the same. Anyone tell you different is trying to justify their higher rates.



4. All the Apple Pro books are great tools for anyone that does video editing. However, my copy of Color came with the top left hand corner of the back cover ripped off. I expected better quality since I was ordering directly from Amazon.