While the Microsoft Architect Advisory Board (MAAB) was still active, I had the opportunity to work with Rocky Lhotka in the Smart Client Architectures working group. I’ve subscribed to his blog for awhile now and flagged both of his posts that software is too hard ( [1] and [2]) to read on my flight up to next week’s SharePoint conference. Today’s mail included a copy of Visual Studio magazine featuring a guest column by Rocky adapted from his first blog post. It was all the nudge I needed to stop and read the article “Software Is Too Darn Hard.”
This is timely advice for all of us in the software industry and certainly for me personally as I focus on services and service orientation (e.g. value yielded, not architectural polish).
1 response so far ↓
1 Craig’s Musings » Blog Archive » I’m starting to see red // Sep 3, 2006 at 2:19 pm
[...] While I may cumulatively spend a majority time and passion developing on Windows in .NET et al during my career, I also work with a significant Java code base at work. IMHO, both of these platforms overshoot the needs of classes of solutions with burdensome (not pervasive) runtimes, prolific APIs, and layer upon layer of functionality with sometimes questionable value (e.g. does this layer justify another part of the underlying platform, framework or toolset, or does this layer yield clear business value?). For example, my previous post about WS-* pain relief is as much about Java’s WS-* implementation as WS-* itself. (FWIW, I prefer Microsoft’s approach in Windows Communication Foundation, which just went Release Candidate, by the way.) [...]
You must log in to post a comment.