Contrary to popular belief...
time to read 3 min | 412 words

Patrick Cauldwell has a post about a set of guiding principal, which I mostly agree on, except:

  • Buy, not build
    • Take full advantage of the platform, even if it only solves the 80% case
      • every line of code we don't have to write and maintain saves us time and money
    • Don't write a single line of code you don't have to
    • Take full advantage of .NET 3.0, SQL 2005, Windows 2003 Server, plan for- and test on Longhorn

    There is a couple of things here that is missing, that is business need and evaluating fitness to do the job. I am pretty sure that Patrick didn't mean to sound this way (by the rest of the post, he & I could argue for a few decades on the fine details, but I mostly agree), but this sound like an approach for a tech driven disaster to me.

    I have seen technological solutions crumble under their own wieght, because their fitness to the business problem was never really considered. "It is MyNewThing, of course it can handle this easily, why, it can handle ten times this load." - But you forgot that scalability != perfromance. The end result was a failed project and a poisioned relationship with a customer.

    Perhaps the only thing that I would add to Patrick's statement is: "When it makes sense to the business problem at hand..."

     

    Tweet Share Share 0 comments
    Tags: