• Eric M Russell (4/16/2014)


    It is possible to create a solution quickly and cheaply and also not sacrifice quality, so long as the scope is constrained. For example, I consider Chipotle Mexican Grill to be Fast, Cheap, and Good Enough (taste, quality, and reliability). Of course, I have to stand in line, choose from a limited menu, and clean off the table when I finish. It's not my favorite, but I've also tried more expensive restraunts with a more elaborate decor and service that failed to meet my personal expectations. I guess my point is that quality and richness of features are two seperate dimensions.

    So it would be more like:

    Fast, Cheap, Quality, Scope; pick any ... three?

    Absolutely agreed except for one thing... people. If you don't have skilled people that actually know what they're doing, then expect multi-colored poop and feathers at all 3 dimensions. That's a pretty big problem for some of the companies that I've visited. For some reason, they think that anyone can write quality code especially when it comes to database interfaces. Between ORMs and some "developers" that don't even know how to get the current date and time using T-SQL and the idiotic schedule expectations that some managers have, none of the dimensions actually stand a chance no matter what you pick. 🙂

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)