Poorly edited and technically subpar
929210
Please, please do not waste your money on this book. The book has errors every other page, the lack of overviews and general depth do not leave you in a position to truly implement these product lines, and I was forced on a number of occasions (see Chapter 9 for an example; configuring the 3000 concentrator) to question the editors' understanding of the technology. I purchase technical books monthly, and have bought Cisco Press on a number of occasions, including the MCNS coursebooks. This was the first time ever that I felt so ripped off that I felt compelled to write the Publisher, and certainly comment publically. Please consider other alternatives.
3381148
The editing and proofreading processes in publishing this book seem to have been bypassed altogether.  This book is ripe with errors and typos that will confuse the unfortunate CSS neophyte.  It appears to be another example of a web-development book that was rushed to press well before it was ready.  I plan on returning the book for a refund.
4345746
The number of grammatical, punctuation and spelling errors in this book made it nearly impossible to finish.  Also, for any fan who followed the series and already knows the various story lines and central characters, this book is at best superfluous.  If you have a genuine interest in "revisiting" the details of all 344 episodes, there is enough material to be found online for free.  If you're purchasing this book believing you will learn anything new about the workings behind the scenes, you are in for a disappointment.

I received a copy of this book as a gift and actually feel somewhat mortified that my friends spent the money.  Because of the generous thought, I'm unable to bring myself to give this a one star rating.  Arbitrary as these things are, I give it two stars for my friends' generosity and because the book is filled with fun photographs taken during the show's original run.

With sincere apologies to the author, who clearly loves the original show very deeply, I cannot recommend this book.  His seemingly endless gushing was over the top and badly in need of tight reins - something which his publishers and editors (if there were indeed any actual editors) failed to provide.
331453
While the premise of the book is good, there is not much that separates this from the rest of the books in this genre. The story was ok, but felt rushed. A lot of things were expanded on far too much (the HALO jump, for example), but the assault on the bad guy's house was so short I thought I missed something.
All that aside, the editing was horrible. I can overlook some misspellings, but corroded arteries instead of carotid? Shoots in place of chutes (parachute). Places where words were spelled correctly, then incorrectly in the same sentence. Grammar and punctuation messed up all over.
4926589
This book is a disaster. It's so poorly edited that all of the mistakes were distracting from the overall story. It was also clearly not proofread or rewritten. There are numerous mistakes that just reek of amateurish effort. In chapter 3 the main character was at the orphanage, Brookfield house. By the time we get to chapter 21 he grew up in Moorfield. In chapter 12 the main character has an appointment with a suspect the following day. The following day is spent in the hospital and on a date, it's not until the second day that the mc keeps his appointment that magically seemed to have been on the second day all along. Another amateurish mistake is a character lifting a glass that was previously empty but manages to drink a great deal of gin from it. Some of the chapters have titles, most do not. This could be some kind of style that the author was shooting for, I don't know. The book alternates between third person omniscient and first person narrative, but it's often difficult to know at the beginning of the chapter which point of view is being employed. I could go on including all the obvious editing mistakes (or lack of editing) but I'm as tired of this book as I can possibly get. I don't know how it ends because I can't stand to finish it, but suffice it to say that if you order this book you will need to shut your brain down completely.
2548221
I regret wasting money on this book.

First, the subtitle is wrong: there are few examples in this book.  There are things labeled "Examples", which list the types of people who are
likely to have the bias under discussion.  For example, the people likely to have Confirmation Bias are "sports fans".  Narrative examples would
be much more useful.

Second, the editing is poor.  There are typos.  Every single right-hand page has "Cognitive Biases Affect on Security" written at the top.
I don't know why that is written there, since it is not the title.  It also is not grammatically correct.  The first sentence in the author
biography is "Mr. Hale is a Computer Scientist with over 30 years of experiences."  From the last sentence of the summary: "sale people"
instead of "sales people".

Third: I suspect that if the average person (e.g, me, or you) spent a little while googling about cognitive biases, they could put together
a book which is better than this volume.  So, do the googling yourself, or buy a different book on this interesting subject.
2966474
Theres a good story concept here. Unfortunately its marred by numerous grammatical errors and typos. Nobody should expect perfection, particularly from a self-published book (even books from the big publishing houses come with them these days) but this book contains so many, it jarred me out of the narrative. The improper use of apostrophes and italics on practically every page got old, as did a number of flat out errors that became annoying (the M1 is an Abrams, not an Abram).

With all that being said, some of the battle scenes are done well. Therres little to nothing in the way of characterization and development, which I don't mind in a book such as this. With a solid line/copy edit, this could be a worthwhile read. As it is, Im sad to say that Im giving up at the 70% mark and moving on to something else.
3907012
Let me start by saying that there is some worthwhile information in this book, however, it was so poorly written and presented, that I barely made it halfway through before finally giving up. I'm not one that usually complains about editing...I get that even an edited book can have errors...but it would seem that the author simply wrote down his thoughts and published it without taking any time to clean things up at all.

I hate leaving negative reviews, and I'm not doing this now to criticize the author, but rather to inspire him to fix this book. I do see value in what he had to share, the delivery just needs to be better if he wants be taken seriously. The cover looks great, so there's that!
3359857
Tons and tons of typos and missing punctuation all over the place.  It could have been a great story, but the poor editing was way too distracting.  Chapter 19, where she introduces the future love interest, begins awkwardly and does not improve much.  Will not purchase another Carey Heywood.

p.s.  Denver is not west of Salt Lake City.  Get a good editor before your next self-pub!
3197717
Terrible editing that I immediately noticed and I am a horrible writer. For example, on question 2 option d is both a and d. Seriously? The errors continue with a case study were, in the same sentence, they refer to the patient as a him twice and a her once. After noticing others errors I didn't bother to finish the book. With such obvious errors in the print in really makes me wonder if the information is actually correct.
2566100
The book is poorly written with grammatical and technical errors throughout. For example, uses "MMB" as a verb with no prior definition, which is not appropriate for a book advertised as a training manual for novice users (what's wrong with "press the middle mouse button"?). Freely mixes different names for the same object or operation, which makes it harder to understand the software and the book.

Contains an uneven mix of gesture emphasis with no conceptual explanation, and conceptual instruction without explanation of how to accomplish the task. Missing steps in several examples, and contains obvious copy & paste errors (which I assume are from some previous edition).

Lots of time spent developing the particular scene, which may be useful if you are planning to reproduce "Surf's Up", but very few explanations of what the tools you use actually do, and no systematic exploration of various settings. For example, you will often be told to set controls to particular values, with no indication of why, what that setting means, how to use it, or when else it might apply. This makes it very hard to generalize, which again hampers efforts to learn the software.

The book is probably twice as long as it needs to be, but contains about half of what it should. A simpler example, consistent terminology, and more logical flow would be a good start. For example, cover polygon, subdivision, NURBS modeling in one chunk, then move on to animation instead of throwing animation, rigging, IK, etc. in between polygon and NRUBS modeling; it will make it easier to understand the set of modeling tools if you don't try to interpose a whole new animation skill set in between.

Many of the illustrations are rendered nearly unreadable because of their microscopic nearly-gray green lines on a 50% gray background (yes, this accurately reflects the unfortunate UI in Maya itself, but that's no excuse -- the other books I've seen on this software increased the line thickness so that the illustrations are at least legible). Further, the illustrations frequently show whole screenshots with little or no indication of which exact features the reader is encouraged to notice.

Too much space is wasted on "make the penguin look like this" in both the text and illustrations. I would prefer some simpler example that gave me a chance to practice the tools to achieve some more obvious result.

The bottom line is that although the book contains a lot of useful information, it is made much less accessible by poor technical writing, an inappropriate example, poor illustrations, and bad organization. Very disappointing, especially given the price of the book and the software, and that this is an official publication from Autodesk.
525433
This book initially interested me because I knew Erik Menendez briefly pre-crime and was interested in seeing how he's survived behind bars. However, I couldn't get past the numerous typos, grammatical errors, and all-around shoddy editing job in this book. They were just too distracting. I got the sense that Erik Menendez might have edited this himself with a smuggled night-light, a Sharpie, and too many prison distractions interrupting his flow. If you don't mind reading a book that screams, "I yam a booke wit no editar," then go for it.
1167090
This book desperately needed an editor. There are multiple typos, recipes with only partial titles, incorrect grammar/punctuation and duplicate recipes under different names.  The formatting was annoying (1.2.3. on some steps, others no formatting)  but perhaps the recipes are tasty?  I won't find out because too many of the recipes use ingredients on the NO list from Plant Paradox; the NO list is even included in the front of this cookbook.  In perusing recipes, I found for example, wheat flour, cheddar cheese, heavy cream and pumpkin from the NO list.  I'm returning and ordering Dr. Gundry's cookbook.
508281
The premise of the story was good; the writing and editing needed help. Detective Lavender and his side-kick Constable Woods discover the body of a well-known actress in an abandoned building. As they try to find whodunit, the rest of the book is taken up with stereotypical characters, cliches, and poor editing.  The love interest is one of the better developed characters.  However, the description of her attraction to Det. Lavender is filled with every hackneyed phrase. Because I got the book, along with the audio book, through Kindle Unlimited, I am not sure of all the editorial errors.  The most glaring error in my reading was something about (I no longer have the book) throwing off the "yolk."  Spell check does not take the place of an editor, or even a good friend who really knows English.
1373085
I read the series within a course of a few days - book one thru book five. Each volume had it's problems but for the sake of this review, I'll keep my comments to this last installment.

Although I found the story idea more than interesting, the writing left a lot to be desired. And the editing seemed non-existent. As someone who works with type, both raw and edited, all day long as a designer and art director for a major metropolitan newspaper, the poor grammar, continuity issues and incorrect words (missed by an automated spell checker because the word itself was spelled correctly even if it was entirely the wrong word to begin with) was more than off-putting. It had me, in fact, literally throwing the book down several times out of frustration.

Darius was often confused with Damian, Aphrodite with several other female characters, too much re-iteration of earlier events had me scanning copy to get to the point.

The idea in the hands of skilled writers or even a competent editor, this story would have garnered 3 and a half stars for effort. As it is, I'm being generous with a two star review.
3600165
Poorly written, even worse editing - lots of misspellings and grammar isues.  Although the topic is important, I could not finish it for all the technical issues as well as inconsistencies in the story.
3780168
To paraphrase another reviewer on here, the author actively makes it more challenging to envision what are very simple concepts. What should be one sentence about a rather intuitive concept, becomes a meandering paragraph. The chapters somehow manage to have little cohesion, and yet include an insane amount of random repetition. This has some of the worst editing I have ever seen in a textbook.