|Problems? Is your data what you think it is?|
mmm. Not sure that counts in the sense I meant. I rarely document how the code works.
I've started to write code that I don't document, in terms of how the code works. When I started to do that, I was uncomfortable, because I was breaking a Rule. Then, I realized it's because the only people who would understand the algorithms and subversions of Perl that I was doing were the very same people who understand why the Rule was broken.
As a Perl hacker I knew once commented ...
And that was all he wrote before the line noise.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
I shouldn't have to say this, but any code, unless otherwise stated, is untested
In reply to Re^2: Re (tilly) 2: Paradigm Shift - Don't use strict