Forewords
Hi, I’m Steve Swartz. Michele asked me to write the foreword for her new book, Learning WCF, because I was one of the two breadth architects for WCF V1. That shows how easy it is to be overimpressed by a title. I am just a pawn in the game of software development. The architect who conceived of WCF and guided our team’s technical work was Brad Lovering, our division’s Technical Fellow. The architect who designed and implemented the core of WCF was Eric Christensen, one of our division’s Distinguished Engineers. Breadth architects like Steve Millet and me were responsible for shaping the parts of WCF into a coherent whole. Each of the parts of WCF was guided by a depth architect and built out by a team of developers, product managers, testers, and documentation engineers. How well you know any one of these 200-plus people has nothing to do with their relative technical impact on WCF. The plain truth is, most Microsoft product team people don’t get out much. We’re a shy bunch overall. The ones you end up knowing are simply the ones who are outgoing enough to become involved with community.
Microsoft product teams think a lot about community. I haven’t counted, personally, but I’m sure the WCF team alone had several million active customers as we developed WCF: people using COM, DCOM, COM+, and MSMQ; people using ASMX, .NET Remoting, Enterprise Services, and System.Messaging; people using WSE; and people using early releases of WCF. Try as we might, it turns out to be impossible ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access