Re: Don't go all PerlMonks on me

[Anonymous Monk]

in reply to Don't go all PerlMonks on me

Just as a counterexample, I have used the "Don't go all PerlMonks expression" to describe to someone that I don't want them writing entire programs in unreadable obfuscated regexen :)

[dana]

You bring up an excellent point. While the help is amazing and my code is much more concise it is tougher to "read"!! Asking for help from bobf means trying to understand when he says 'toss it into blah blah blah module and there you go'....to which my comeback is usually 'HUH'??? He is much more articulate than I. :)

[bobf]

the help is amazing and my code is much more concise

Thanks! I think "amazing" is a bit more than I deserve, though. :-) No, I did not pay her to say that.

it is tougher to "read"

Well, I hope I never help so much that you don't understand what the code is doing - that's certainly not the intention.

Code readability is in the eye of the beholder, and striking an effective balance between concise idioms and step-by-step explicity is an art that is best appreciated at a given point in time (since that balance will likely change over time, especially when just starting to learn Perl and getting more comfortable with common Perl idioms). See threads such as What is code readability? and Should I leave behind beautiful code or readable code? for more discussion and debate on this topic.

For the record, I don't think I've ever told you to toss something into either Acme::BlahBlahBlah or Yada::Yada::Yada. ;-)