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

use Perl Log In

Log In

[ Create a new account ]

cgrau (3787)

cgrau
  (email not shown publicly)
http://sirhc.us/

Journal of cgrau (3787)

Tuesday July 25, 2006
07:03 PM

OSCON 2006, Day 2: More Perl Best Practices

[ #30426 ]
My second Damian tutorial. It would have been my third, but I passed on his Vim tutorial. I've grown more disappointed since yesterday afternoon as I continue to talk to people who rave about Damian's Vim tutorial. Maybe next year. Assuming I can convince Qualcomm to send me again.

The title of this tutorial is More Perl Best Practices. It seems this is a sequel to Damian's Perl Best Practices tutorial at OSCON 2005. I'm not sure how much I'm missing by not having seen that tutorial. Fortunately, this tutorial merely adds to the last one, rather than building upon it.

Tutorials like this are not for those with an overabundance of ego. Damian's best practices are not necessarily my own practices. I use tabs instead of spaces, I cuddle my else statements, and I don't break my lines before operators.

Perl best practices are really Damian's Perl practices. However, he has gone to great lengths to create compelling arguments for each of his practices. For this reason, I intend to at least give each of Damian's practices a chance. I may even come around and make some, perhaps all, of them my practices.
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.
  • I use tabs instead of spaces, I cuddle my else statements, and I don't break my lines before operators.
    Is he seriously talking about that kind of stuff? Good grief.
    • The code layout section was maybe 10 minutes out of a three hour tutorial. And it focussed on the underlying perceptual psychology of layout decisions in terms of communication theory. So, yes, you are precisely correct: the specific way of was talking about "that kind of stuff" was seriously.
  • Perl best practices are really Damian's Perl practices.

    Some of them certainly are. Mainly the ones related to layout, which I did point out up front: "DON'T MATTER" ;-)

    However, whether they were specific to me or more generally agreed upon (in the introduction to the book there's an extensive list of well-respected Perl developers who contributed to the final set of recommendations), every suggestion I made is based on providing solutions to genuine problems and/or traps in Perl. I also pointed out