• Phil Factor (9/30/2013)


    I once wrote

    'the best development teams I’ve worked on embraced the whole gamut of humanity – a wild mix of cultures, sexuality, motivation, age and beliefs, spiced with maverick spirits and eccentrics. The result being that everyone was jolted out of their complacency, both professionally and personally, and learned to challenge assumptions rather than accept them.'

    I still stand by that opinion.

    Now THAT I agree with... especially the complacency thing. Too often I find developers that just want to "get it off their plate". Too often I find developers that take no ownership of any given problem nor even ownership of their own code.

    The phrase "maverick spirit" sometimes bothers me depending, of course, on how one defines the word "maverick". I absolutely love the "mavericks" that come up with different and, many times, better ways to do something. "Best practices" many times come about by some "maverick" testing for oolies. On the flip side of the coin, I absolutely hate "mavericks" that implement those things without discussion with the rest of the team or any practicle testing because they don't necessarily know the ramifications of their "improvement" as they also don't necessarily know the big picture.

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