If no one has read the Ask the Wizard blog, don’t worry – I subscribed only yesterday. Although this is mainly a business post focussing on how building the back end of a service gives you more flexibility in the products that go live, I see a great many parellels with software development.
Much more simple to understand the FeedBurner example. We didn’t spend the first five months building those two services we rolled out in February. We spent the first five months building out the architecture for feed filtering and feed processing such that we could quickly deploy any new feed service we decided to build, and then we spent about a week building out those first two services. Yes, it was true that somebody could have built a competitor to what we launched in a weekend. However, we would be able to quickly iterate and innovate on top of our release, whereas the built-in-a-weekend competitor would have to keep building one-off services that would eventually either become untenable or require an incredibly long period of underlying architecture refactoring while we continued to innovate.
In software development, you can get right in there and do your bit. But thats all that your software does. If you spend the time creating a framework that supports the code that you later write, then its so much easier to add features and services becuase the framework has already been build and all the really complex stuff goes on under the bonnet. I supose it comes down to the adage: build it right the first time.
Random Musings 