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
every Perl script that says:
"Don't be stupid."
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Naming nazi (Score:2)
I'm real big on naming, too. Although I'm not often in a position to name a project or product, I obsess over the name of each report or program I write at work and over the names of variables in my programs. Why? Because when the thing you are working with is ineffable, you often have a vaguer idea than you should about what it is. If you think long and hard about what it is and name it so, you'll usually have a clearer idea of what you're doing. I've seen enough counterexamples in my own and other people's work to convince me of that forever. :)
After realizing I held this philosophy and mentioning it to my coworkers, I was gratified to hear in one of my software engineering classes that some OO-heavy development philosophies really emphasize naming. Apparently others have noticed that if you can't say what it is, you probably shouldn't be working with it. :)
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Reply to This