In 2005 a whole batch of new Perl titles were published. My favorite among them is Perl Testing, by Langworth and chromatic (with HOP a close second). At the beginning of chapter 3 (p. 39) the authors write:

All the normal rules of programming apply to tests: stay organized, reduce duplication, and don't take on more technical debt than you need.

"Technical debt"??? I've never seen this term before. I have a vague sense of what the authors mean by it, but for my edification: what are common examples of "excessive technical debt" in the Perl world? Tied variables? Lvalue accessors? Source filters? Or is it something even more mundane?

Needless to say, I'd love to read a meditation or two on the issue of Perl-world Technical Debt (hint ;) ).

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.