|P is for Practical|
Re: Commonly accepted style guide?by sauoq (Abbot)
|on Sep 25, 2005 at 07:21 UTC||Need Help??|
Firstly and most commonly: poor function names. Secondly and almost as common: poor variable names. Thirdly: poorly written comments.
If I see @n[$i] I get very worried.
Good function names, variable names, and comments.
Generally and to some extent, yes. But there are lots of exceptions. There are some capable but entirely self-taught developers who have peculiar styles and I've seen some really lousy Perl code written by very good C programmers. At the extreme lower end of the scale, though, it's usually easy to judge experience, at least with a particular language.
Sure. How? That's a big question. I guess a concise way to put it is that my code has gotten more expressive. By which I mean that my intentions are, I think, more transparent to the reader. Another shorter way to put it is that my code makes more sense these days... ;-)
-sauoq "My two cents aren't worth a dime.";