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.
  • All the answers here make the assumption that someone, other than you, wants to improve the code. Going forward with only you wanting to change the code means that you'll be perceived as saying "This code sucks, and I think it should be done this way."

    If nobody sees a problem in the code, then your first task is to help the person see that life could be improved by improving the code. Coming in and saying "This could code be better" doesn't mean anything, because "better" is a fluffy word. Why is it better to use qw instead of splits? Why is indentation better? Why is it better to use existing libraries? These are obvious questions to you, but to a novice who write code that has never answered these questions, they're not. You must answer those questions for the person.

    --

    --
    xoa

    • Which is what option #3 that I made up boils down to – wait until MJD finishes writing down good answers to these questions and then give them to the novice to read. I’m not entirely serious with that, but it’s not meant as as much of a joke as it might first seem, either.

      (I am quite looking forward to that book. I am nearly (though of course never completely) certain that it will hold no big revelations for me, yet I am equally confident that I will enjoy it.)

      • But "here, read this" is the same problem. The novice needs to want to change something, to get a benefit, in order to improve.
        --

        --
        xoa