Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Head First C#

I just finished reading chapter 1. The casual tone of the book definitely makes learning easier. But it's obvious that this book was rushed to the printer. I found at least a half dozen errors in grammar and sentence structure, not to mention several missing words. I'd be tempted to ask for my money back if I wasn't enjoying the book! Maybe Colleen Gorman needs an assistant ;-)
1 person has
this problem
  • Hey Brian-

    First, thanks for taking the time to speak up... I'd rather someone say something about a problem than be quiet, as it doesn't give us a chance to fix it (or at least let you know what went on).
    In this case, you nailed both the problem and reason behind it on the head: we did indeed reduce our normal production cycle for Head First C#. When it came down to it, we had to make a choice: do we want to wait a month to get this book out, and fix all those grammatical errors you found, or would we rather get the book out quickly, especially when we had a large number of people waiting on the title (something we can gauge based on book store demand and our own forums).
    In this case, we decided getting the book out was important. We talked about things at length, and that seemed sensible. Let me pull back the curtain a bit and give you some more about why we made that decision:

    1. We were and are confident the book has been meticulously reviewed (twice, in fact) for technical errors. So while there may be a spliced infinitive or missing comma, or subject and verb might not quite agree, we're positive we correctly and clearly explained how to use LINQ and why you want to know exactly how double-buffered animation works.

    2. The Head First books are already pretty casual and conversational in tone. While that does not excuse grammatical errors in our eyes, it does mean that a little looser standards in terms of where a comma goes or it you use "were" or "was" can slide by. Again, that's not to say we don't care, it's merely to say that we recognize our readers expect and are okay with a slightly looser feel in terms of the prose.

    3. Finally, and most important, we always ask, "What serves our learners, our readers?" In this case, we felt that most learners would really want the book NOW with some non-technical errors, than wait another month to get those things right.

    I hope that sheds a little light on why we did what we did, and even makes sense :-) As always, we love hearing from our readers... so thanks for posting.

    Brett McLaughlin
    Series Editor, Head First
  • (some HTML allowed)
    How does this make you feel?
    Add Image

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited indifferent, undecided, unconcerned