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 ;) ).
the lowliest monk
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Technical debt?
by dws (Chancellor) on Dec 21, 2005 at 17:22 UTC | |
by adrianh (Chancellor) on Dec 21, 2005 at 19:07 UTC | |
by tlm (Prior) on Dec 21, 2005 at 17:27 UTC | |
Re: Technical debt?
by BrowserUk (Patriarch) on Dec 21, 2005 at 18:01 UTC | |
by hsmyers (Canon) on Dec 22, 2005 at 15:46 UTC | |
by BrowserUk (Patriarch) on Dec 22, 2005 at 16:18 UTC | |
by hsmyers (Canon) on Dec 23, 2005 at 16:14 UTC |
Back to
Meditations