I appreciate that strong feelings about our books can cause opinions to swing both ways. People who like our books the most when they are good are the ones who feel most let down when they aren't as good.
Why the errors?
I don't think it was entirely haste because we did spend a lot of time on this project, despite that fact that we had it done soon after ASP.NET 2.0 released. We did multiple rounds of tech editing on this.
The writers? Sure, I think they'll admit that in places, they introduced errors that they're sick about. Dave mentioned this in responding to some errors on the C# version of the book.
The editors? I don't place the individual fault there either. I know that the tech editor caught and helped fix many things.
If there's one thing I want to try differently and am experimenting with how to handle in our book process, it's that the highly experienced authors and tech editors we hire, sometimes overlook an error in an easy things they've done 100 times. I want to try to work on a process that will get novices, first time users to the software, especially on our "Beginning" books, somehow involved in the review process to spot these things that all the experienced pros miss. I have to balance that thought with not overwhelming the authors with extra incorrect questions from the novices for the authors on things that are correct but the reader did wrong.
Senior Acquisitions Editor
Wiley Technology Publishing
Jim's Book of the week: No book this week - Donate to the Red Cross!