Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • The first one is to try to code things in a straightforward way that anyone can understand. That means laying things out clearly, using a widely understood group of features, etc.

    The second one is that if I break the first rule, break it hard. If I really need to be really tricky, get all of the trickiness out of the way in one place. If I need to use an advanced feature like overloading, use it a lot so that anyone who has to work with the project will quickly be clued in that it is going on and how it works.

    Following those two rules works pretty well. Particularly if I'm the user who has to read the code 6 months later. (Which is usually the case for me these days. I don't think that anyone has read more than 20 lines of the Perl that I've been written in the last year...)

    • Is this what Einstein meant when he said:

      Make everything as simple as possible, but not simpler?

      How is it possible to make something simpler than is possible?

      • How is it possible to make something simpler than is possible?

        Everything is an object, in Java, even if you don't need it to be an object, in which case it's either a primitive (for efficiency), or namespaced global functions (a class full of static methods) -- but everything is an object in Java, because that makes everything easy.