Jon Udell: Road to managed code. "What .Net will do for the server family, sooner rather than later, is present a consistent set of interfaces to programmers. These interfaces will live in managed space as part of the .Net Framework and will enable any .Net language to control the servers. [...] the server products will become a set of components that can be scripted using .Net languages. This arrangement will enable developers to extend individual servers more productively, and it will be a huge win when -- as is typical -- they yoke different servers together in complex solutions." Interesting. Managed code is one of the key concepts of .NET Framework.
Blunt Force Trauma: In the Same Room Does Not Mean on the Same Page. "I can tell you that when 27 people walk out that door to go their 27 separate ways, they hold 27 different ideas about what they heard, what it means, and what they should do about it." And even if they agree that they ARE on the same page, it doesn't really mean that they ARE on the same page, because the real understanding of what "the same page" means is different for all of them. Sometimes completely different. Jumping communications gaps. Excellent article based on Agile Software Development by Alistair Cockburn.
toolbox: Preparing .NET updated. More than 80 links added; some definitions were deleted (.NET My Services), some updated (smart devices) and some added (.NET Development).
One more thoughts provoking presentation from M. J. Dominus: "Design Patterns" Aren't. "How can you distribute responsibility for design through all levels of a large hierarchy, while still maintaining consistency and harmony of overall design?" Does anybody see the analogy with NLP principle: The Map is not The Territory? "One form of limiting map is what I like to call "questionable prerequisites". These take the form "I have to do (or have or be) this before I can do (have, be) this." A beginning coach might assume, "I have to be certified (or have a brochure or have more experience) before I can approach business clients." An employee might assume, "I have to be invited to work on this project." An individual might assume, "I have resolve all my own issues before I can have a meaningful relationship." OR, The coach could just start talking to people about coaching. The employee could contact the project leader and say they are interested in working on the project. The individual could enter a relationship as an imperfect human!" Isn't it the same kind of limitation we experience applying patterns? BTW, Mark, your advice worked great for me. Thanks.
Microsoft Architecture Overview: Executive Summary. "This document is intended for business, software, and infrastructure architects who want to understand Microsoft's approach to enterprise, application, and technology architectures. It covers architectural terminology, patterns, concepts, and definitions as a series of views or levels of architecture."
Microsoft: Patterns & Practices. "Patterns and practices contain specific recommendations illustrating how to design, build, deploy, and operate architecturally sound solutions to challenging business and technical scenarios. The technical guidance is reviewed and approved by Microsoft engineering teams, consultants, and Product Support, and by partners and customers."
Microsoft: .NET Architecture Center. "The .NET Architecture Center is a new site devoted to business, software, and infrastructure architects. The Center is a collaborative effort involving Microsoft product teams, MSDN, TechNet, and Microsoft's new Architecture Review Board, and it spans the boundaries of MSDN, TechNet, and other sources to serve multiple perspectives, or views, of enterprise architecture."
toolbox: YAWINP (Yet Another What Is .NET Piece). ".NET = .NET Servers + .NET Framework + XML Web Services + smart clients + user experience"
John Udell: Glue, Gaia, and the services grid. "As every user of Glue knows, Graham [Glass, the wizard behind The Mind Electric] is more than a brilliant software engineer. He has an even rarer talent for simplicity. In Glue, as Larry Wall says of Perl, "easy things are easy, and hard things are possible." That's why I think of Glue as the SOAP::Lite of Java. The easy thing that Glue makes easy is the basic web services stack. The hard thing that Gaia makes possible is a grid fabric which, though intended first for web services, has more general possibilities." Hm, "Glue as the SOAP::Lite of Java". I like that. Thanks, John. Agree with everything you said about Graham and Glue. Glue is super simple and easy to use. Sometimes it's even simpler than SOAP::Lite ;). Kudos Graham!