Slashdot Mirror


Custom Software vs. COTS Products

andy1307 writes "Nicholas Carr, best known for setting off a firestorm with his "IT Doesn't Matter" article published in the Harvard Business Review, has an op-ed in today's New York Times arguing against the use of custom-built software in favor of off-the-shelf products. He cites the example of Ford scrapping a custom built software solution for buying supplies. He says companies, frustrated by the failure of custom built software, have taken to modifying their business processes around the packaged software solution. The most unbelievable line in the op-ed: "When it comes to developing software today, innovation should be a last resort, not a first instinct.". Most of us know of failed projects using off-the-shelf products that need minor customization. Is the track record of custom built software really that bad?"

2 of 325 comments (clear)

  1. a perfect example - Nike and i2 by trolluscressida · · Score: 2, Informative

    didn't Nike have a billion dollar failure using i2? So much time and money for a project that they eventually had to toss - it wasn't even close to performing for them as needed. Most out of the box packages end up needing so much customization that it seems to be easier to come up with a solution from scratch. At least that way your company will own the code and (hopefully) know what it contains.

  2. Re:are you a restaurant? by BigGerman · · Score: 2, Informative

    Gee where are my mod points when I need them?
    But seriously, the formula for success that I observed for many many years in the game is - custom applications built on OTS components/frameworks, preferably OSS frameworks.
    This gives you best of both worlds - good, custom solution and speed of development based on not reinventing the wheel.