• Dalkeith (10/22/2012)


    I personally support this fully and I agree with a strategy of developers supporting their products throughout their entire life.

    I have to say that I don't agree with that. What do you do if the developer goes on vacation, gets sick, leaves the company, gets promoted, wins the lottery, or flat out dies?

    This is what teams and cross training are for. Although individuals may create parts of the product, the team must eventually support it so that no one individual becomes indispensable.

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