in reply to Re^2: Meaning of Maintanability and Functionality in Coding Perl
in thread Meaning of Maintanability and Functionality in Coding Perl

Perl Best Practices (aka PBP) isn't a Perl version of Code Complete (aka CC). While they certainly address the same basic topic (how to write maintainable code), CC provides a lot more detail in terms of why these practices are better than the others. PBP references no studies and works only in one language. I would recommend reading both books.

As for CC being dated ... yes, it was written over 10 years ago. I've also worked on at least two major projects that are around that age ... written in Perl. Plus, nearly every app I've ever worked on has had to interface with another application that's over 10 years old.

I would put forward that most applications are either under 3 years old or over 10. My theory is that every app is either new (under 3 years old), in the process of being rewritten, or it's survived. And, yes, 3 years old is new.


My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
  • Comment on Re^3: Meaning of Maintanability and Functionality in Coding Perl