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.
  • Look, I tried to learn Object-Oriented design. I really did. I knew software engineering was absolutely the most important area in my studies. I shelled out thousands of dollars for a bachelor's degree and most of a master's degree. I took software engineering as an undergrad and got a jerk of a professor who didn't teach a thing. He was the only unsatisfactory professor I had. At the end of the course I seriously considered going to the dean's office and demanding my money back and credit for the cou

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • I've read (okay, skimmed) a lot of software design or OO design texts, and I've found similar things. Most of them suck, a lot. (Even our books have occasional howlers [oreillynet.com].) If I'm right and the design of Java can mitigate some of the damage of bad use of OO, then this doesn't matter so much for Java users; their programs will tend to converge on the local maxima which happens to be only slightly better than the global minima.

      For programmers in languages which lack the "Everybody buckle up" philosophy by default, you can perpetuate some truly awful hacks without knowing it.

      J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers. Most of the other million or so Perl programmers don't have that advantage. They don't get taught Perl in school, the Really Great Books All Programmers Should Read almost never include Perl, and the belief that "Hey, it's a scripting language and not all that serious, you can just whipuptitude something quickly in an afternoon" way in which many of them first encounter the language doesn't exactly lead itself to high disciplined programming right from the start. It takes a decent Perl programmer to read Design Patterns and see how to apply those ideas to his or her code (or, better, how many of them aren't necessary if you use Perl effectively). A Java programmer can just cut and paste the examples.

      I'm not sure either way is more optimal than the other, and I'm not saying that bad Java is any less bad than bad Perl. However, it is my experience that most bad Java code is bad in similar ways, thanks in part to the language design.

      • J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.

        I think I'm going to put that on my resume. :)

        --
        J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
      • Anyone know if O'Reilly's Head First Object-Oriented Analysis and Design [oreilly.com] is any good or not?

        --
        J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers