Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • These are the sort of clients who won't listen to reason. Have you showed them an itemized list of $$$ billed for fixing their mistakes? And how much larger it is compared to just writing some sanity checks? That sometimes opens people's eyes. And if it's only a few hours, wouldn't it be worth it for your company to just eat the time and be able to call the client first to tell them they screwed up? I've always loved showing someone that the "bug" is really their error. :=)

    You have to figure out if the ex

    --
    "Perl users are the Greatful Dead fans of computer science." --slashdot comment
    • I can't help but wonder if your title was a typo -- 'me versus 'em :)

      We have broken this down for them before but the response is typically something along the lines of "once we nail this thing, it won't change any more" (which, of course, is the reason most of us with jobs still have them.)

      You are correct in thinking that giving up the ongoing revenue from their stupidity is worth my sanity, but I have three other problems with issue. First, I hate to have a system that I know is wrong. The data vali

      • The final problem with this is simple: every time I have to fix this, it drives up costs for other customers as I get pulled out of the "groove" and have to spend time figuring out where I was with the work I was originally doing.

        This sounds to me like the customer problem is masking a management problem, or perhaps an impedance mismatch between you and your management. From what you say, they seem a lot more comfortable with exchanging reputation for money than you do.