The SOAP/WS* Debate: Raymond Chen 0, MSDN 1
"If you don't understand all the specs, don't worry about it. Tools are being created by people everywhere to make it so you can just indicate the capabilities you need, and the rest will be done for you," said Matt Powell, a content strategist at Microsoft's developer network, in a posting.
I take this as encouragement to use technologies that you don't understand, and I, um, don't understand that. I just can't think of a more common reason for projects failing.
If you go to the source of this quote, you'll see an interesting discussion at the bottom. Joel's spot-on criticisms are alluded to in the "Leaky Abstractions" comment, and I thought the whole discussion exuded a major "Raymond Chen vs. MSDN" vibe.
People are finally (slowly, very slowly) figuring out that using SOAP for departmental apps just because Visual Studio makes it easy might not be the best idea. Is this any different than the Java folks figuring out that EJB might not be the best technology to build non-distributed systems (aka standard LAMP-like web applications)?