Is it so hard to document what we do? I think so. Otherwise there would be more information out there on stuff. I'm just talking about the stuff we know about. There is so much untapped knowledge that there probably isn't time to write down what we all know--now imagine what we could know if we would just take the time and write about it.
Our upcoming book is just a sliver of what the Engineering and Ops teams know; but it needs to get "out there". The working title is: "Microsoft Office SharePoint Server 2007 Engineering and Architecture Resource Kit".
This is a text that will be the prescriptive guide to architecting and engineering a successful, large-scale implementation of MOSS 2007--written by Microsoft Architects and Engineers. There are a number of books out there that speak to both WSS and MOSS. All of them are for *Administrators*, the emphasis being on Administration. This book will be a 'nuts-and-bolts' text of the "why" more than "how". The book will be similar to a "Notes from the Field" but from an Engineer's perspective, not an administrator; a book on “How Microsoft does IT.
We have a lot of SharePoint Engineers and Architects who have expressed a deep interest in participating; from all areas of the company, such as the Product Group, Engineering (IT), Engineering (MMS), Marketing, etc.