John,

>The stuff always has to be tested. And, a TE does more than just test code. You are over-simplifying the role of the TE.. Maybe my standards are just higher...

It is clear (to me) that you do not have sufficient experience with me as a technical editor to accurately comment on my technical editing abilities.

So, to help you gain that experience, I am proposing a win-win-win project for your consideration. Send me by email a couple of chapters of your upcoming book, or upcoming magazine articles or white papers, preceeded by an NDA if you wish. You can even seed the chapters with intentionally inaccurate information. A few days later you will receive my technical editor's markup. All of this will be done in private.

Then, we can resume this thread from a more informed point of view.

Win-Win-Win:
1) You and your book benefit from my input.
2) I gain from seeing your material before most others, and from honing my editorial and technical skills.
3) UT'ers benefit from less hot air.

Just one ground rule: If we resume the thread after this little project, I will be free to comment publicly on your writing skills (limited by NDA) if you comment publicly on my editorial skills.

This is not in jest. I'll be watching my inbox.