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.
  • mjd did write about this in his blog: Just put it in the damn object! [pobox.com]
    • Yeah, I actually linked to that about mid-way through the post; that'll teach me to bury the lede!
      • D'Oh! That'll teach me to just skim the article and not follow all the links. I thought I was helpfully providing what you asked for in footnote [2]. But about cargo cult programming [wikipedia.org], I think you're a little too hard on yourself. You obviously understand the reasons to avoid putting things in Perl objects and how the alternatives work. mjd sums up my understanding of cargo cult programming in this entry from his File of Good Advice [google.com]:
        #11900 You cannot just paste code with no understanding of what is going on and expect it to work.
        There's lots of similar "advice" in that file, including the lucid "#11959 Cargo-cult." But that's not really a "writeup", so probably isn't what you're looking for. If anyone else knows of a writeup by Mark Jason Dominus on cargo cult programming and/or behavior, please share.
        • A-ha! I remembered it was on his blog, and that it didn't have cargo cult in the title: Creeping featurism and the ratchet effect [pobox.com]. In particular, toward the last third of the post:

          By saying "if you're not sure, just avoid the problem" we are encouraging this kind of fearful, superstitious approach to the issue. That approach would be appropriate if it were the only way to deal with the issue, but fortunately it is not. There is a more rational approach: you can look it up, or even try an experiment, and