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.

Switch 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I do feel bad for you, but the Mac is not the problem as much as your process is. Don't use a newly upgraded machine for such a thing, or at least find a way to doublecheck the work before assuming it worked properly.

    Not that most of us wouldn't have made the same mistake, but I do believe it was a mistake on your part moreso than a bug in Mac OS X. That is, it is a bug in the OS, of course, but the bug didn't put you in the situation you're in is more a problem of the process than the OS. Heck, this co
    • Yep. Always check your work. Always doublecheck anything important. Always triplecheck anything critical.

      I always remind other people to do that. Eventually, I may even remember to do it myself. :-)

  • ...that's a pretty harsh way to find out.

    Pudge has a point -- never rely on new stuff when it's this important. Of course, personally, I'd be more than a little angry even in a non-production situation.

    Screwing up a burned CD because I was running lots of programs -- my fault, and I should have known better. Having a burned CD that won't work on another major OS -- their fault, but I still should have known better.

    This makes me feel better that the school where I'm going to be doing my internship is

    --

    ------------------------------
    You are what you think.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.