That is exactly the kind of article that I'd like to see more
of. The reasons I like it:
- It examines code that I could have written
- It explains exactly what the code is trying to do
- It breaks the code into manageable snippets
- It shows a better way to accomplish the same goal
- It explains the better way to accomplish the same goal
- It creates vocabulary to discuss the concepts behind better
practice.
I would really like to see a section like this here, written in
cooperation between an experienced perlmonk and a less experienced
perlmonk. Naturally, the teams could rotate, and maybe somebody
could choose at random the teams, granting extra experience on perlmonks.org
for a contribution that is worthy.
