>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?

I'd say that falls under the heading "peer reviewer." I'll ask a researcher friend of mine how her technical journals handle this, but I believe that the peer reviewer would review experiment results and design, which is what I think you are talking about.