Home Forums SQLServerCentral.com Editorials Quality Over Timing RE: Quality Over Timing

  • March 9, 2011 at 1:07 pm

    #1296767

    Mark W Johnson (3/9/2011)

    krowley (3/9/2011)

    When you don't know if a feature will really meet the needs of your users because they don't really know what they want themselves, it just makes a lot more sense to focus on speed over quality, since spending a lot of time getting a feature perfect when in the end it won't really meet the business need of the user just makes no sense at all.

    I think you nailed it on the head there!

    Again, this is where I talk with the user because it makes no sense to write code for something the user isn't sure of.

    --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)