I am hearing the word "multisourcing" more often lately. It was part of a recent Gartner conference, among others. While the word in itself doesn't mean much - there is a nuance here that helps a little to explain what's going on in software development today. It's not simply sending your development task off to someone else to do for you (outsourcing), it's more about using the best source for appropriate code - and probably several. So today's software projects almost certainly use some open source code, they may have commercially licensed code, probably some written in house, as well as some developed elsewhere under contract. All targeted to a single architecture. When done successfully, the result should be better code, sooner - and potentially at lower cost. All of which makes the question "what's in your code?" more important than ever.
Is there manual, examples, books no how to properly build multisourcing software?
Posted by: Andrew | May 16, 2006 at 04:12 PM