OK, what about testing code. Lets say that I am proposing a specfic technique about SQL Server Stored Procs. You are the TE of the book. You are charged with the responsibility of both testing the code and making sure the text makes sense from a technical standpoint. If you have never done C/S work or if you never worked with SQL-Server, how would you effectively do that job?

>>>
>>FWIW, you might want to check something out about the profession of technical writing.
>><
>>
>>I am not disputing what a technical writer does. In other words, somebody could be a medical writer without being a doctor. However, at some point, somebody with the necessary technical knowledge has to validate the piece...
>>
>>Agree???
>
>Absolutely! Peer review is critical, and what you are, I believe, refering to. Perhaps part of the difficulty here is that these two functions are being intertwined.
>
>>How about my example with the Hentzenwerke C/S Book???
>
>If the Chaim Caron is technical editor then, no, he doesn't have to have done C/S programming. If he is doing the peer review, then, yes, of course, he would need experience.
>
>It sounds like the differences (critical, in my mind) in roles are not being clearly understood. Much like how, in traditionally run development projects, we've confused design and coding.