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

  • Creating Reactive Applications in .NET

    In modern applications, data is being retrieved in asynchronous, real-time streams, as traditional pull requests where the clients asks for data from the server are becoming a thing of the past.

  • AI for GitHub Collaboration? Maybe Not So Much

    No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.

  • Visual Studio 2022 Getting VS Code 'Command Palette' Equivalent

    As any Visual Studio Code user knows, the editor's command palette is a powerful tool for getting things done quickly, without having to navigate through menus and dialogs. Now, we learn how an equivalent is coming for Microsoft's flagship Visual Studio IDE, invoked by the same familiar Ctrl+Shift+P keyboard shortcut.

  • .NET 9 Preview 3: 'I've Been Waiting 9 Years for This API!'

    Microsoft's third preview of .NET 9 sees a lot of minor tweaks and fixes with no earth-shaking new functionality, but little things can be important to individual developers.

  • Data Anomaly Detection Using a Neural Autoencoder with C#

    Dr. James McCaffrey of Microsoft Research tackles the process of examining a set of source data to find data items that are different in some way from the majority of the source items.

Subscribe on YouTube