Post reply

Why Would You Do That?

  • December 9, 2024 at 12:00 am

    #4493816

    Comments posted to this topic are about the item Why Would You Do That?

  • December 9, 2024 at 1:08 am

    #4495171

    It's gotten to the point where I evaluate changes by determining how much harm the change causes or how little a required change brings to the table compared to the work it now takes to do the same thing or less (feature loss).

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

  • December 9, 2024 at 8:28 am

    #4495313

    Jeff, do your teams have any tools to help them identify the impact of their change?

    Years ago a senior developer said, "I hear you and want to help you but we simply don't have access to the metrics you use, let alone the background knowledge to understand what they are telling us".

    I've found that most teams have only the vaguest idea where data they collect is used beyond the bounds of their application.  So much so that at least one team deprecated the part of their app that collected the transactions on which we got paid.  More worryingly, no business person picked up on that omission.  It was only when the Finance department started reporting sales falling off a cliff that the penny dropped.

    As DBAs we are privy to a lot of the plumbing and pipework that allows the business to function.  That gives us a lot for insight but somehow I feel that we have accidentally acquired accountability without authority.

    LinkedIn Profile

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply