• ...but it takes participation and rational, reasonable debate, not childish exaggerated complaints and insults. We want to influence and convince, not upset and anger.

    I'm thinking that needs to become a two way street with software and hardware vendors as well as service providers. People pay big bucks for that stuff and, especially when things don't work as advertised or the advertising for certain features is misleading, people are naturally going to be upset when things go bump in the night.

    Then there's the "fine print" rule. I recently ran into a problem with two features of some very expensive software that advertised certain advantages because of the features only to find an exception buried almost as casual note in a seemingly unrelated chapter that rendered these rather expensive features virtually useless. One of the features has been fixed in the next release but there's no retrofit for people who bought the current version of the software just to get the feature. Instead, those people have to pay even more to get the next version.

    It's nice to say that "rational, reasonable debate" should be used instead of "childish exaggerated complaints and insults", but people shouldn't have to convince vendors to do the right thing. Complaints about something not working, even if it only seems logical that they should work, is anything but childish. The insults come when the vendor or service provider has built up so much technical debt in their product that they can't possibly please everyone and elect to please virtually no one by continuing with their interrnal plans instead of taking a step back for a moment.

    You also have to consider what a "childish insult" is or is not. If you're on the receiving end of poor product, especially product that was working very well and has been changed for the worse, then the given insults aren't going to seem so childish. In fact, since many vendors and providers simply don't listen, sometimes you have to insult the hell out of them just to get their attention or to get them over the "management direction" hump.

    Vendors need to start producing products that have a whole lot less bugs and it shouldn't take even a profesional "mob" to convince them. They also need to go back and fix things in previous versions instead of punishing customers for being loyal.

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