Developer's Toolkit

Blog archive

Building Modern Software

I'm at the VSLive conference, speaking at the co-located Software Architect Summit (SAS). I'll provide a couple of posts discussing specific sessions over the next few days. My first is the Tuesday morning keynote.

David Chappell (Chappell and Associates) gave his usual rousing presentation of how the future of software is in services, and the role of Microsoft solutions in that future. Microsoft is in the process of taking several of their object and services technologies and abstracting them into a single approach to developing services-based applications. This is the technology that has been the focus of the last couple of major Microsoft conferences (including the last San Francisco VSLive) -- Indigo, or Windows Communications Framework.

It's a difficult pitch to make to coders, many of whom don't think far beyond the immediate impact of their code or their specific project. It's doubly difficult when you fit in a product pitch for Microsoft's next generation of tools and infrastructure (although David is such an accomplished presenter that it flowed smoothly).

At the beginning of the talk, David described the connections (none but the same name) between himself, the comedian David Chappelle (not present), and David Chappell (Sonic Software, and a colleague of mine), who was in the audience. The amazing thing was that David (Sonic) did not get up in the middle of David's presentation and shout, "It's an ESB!" The combination of Biztalk Server 2006 and the Windows Workflow Foundation contain pretty much what the non-Microsoft world thinks of as the Enterprise Service Bus. It would be a great debate if we could get the two of them in a room talking about that (although it would be very hard to moderate – "Your turn, David, er, Mr. Chappell, oh, forget it!").

David also compared the role of the software developer to that of a liquor salesman, describing his own days as a musician in his youth. "Whether or not I got hired back depended entirely on how many drinks they sold that night." Ultimately, software developers have day jobs because someone is willing to pay for the results of their collective endeavors (don't tell Richard Stallman that, though).

But it is clear that developers, whether working with Microsoft, Java, or other platform and set of technologies, must make their code more open and accessible to both automated and human interaction.

Posted by Peter Varhol on 01/31/2006


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube