http://www.perlmonks.org?node_id=989153


in reply to Re^2: Practical example of "Is Perl code maintainable"
in thread Practical example of "Is Perl code maintainable"

I wouldn't call you names but–

  1. Of course Perl has comments.
  2. Besides taking up space and concentration, comments drift and end up being lies or broken crutches a lot. They should only clarify what the code and the Pod (and the unit tests for that matter) cannot.
  3. That the code presented isn't runtime application of composed roles and mixins built dynamically with business logic stored and versioned in the DB, it's a basic file check one perldoc away. It doesn't warrant even a correct comment.

  • Comment on Re^3: Practical example of "Is Perl code maintainable"

In Section Meditations