Thursday December 19, 2002
"Is PERL the most optimal way?"
I've been working on a smallish but vital system (written in Perl, or course) for the past few months. The other day a question came down from VP to Director to me: "Is PERL the most optimal way for us to do that?"
now, that's about the most loaded question I can think of - probably rooted in the old Perl == CGI idea, washed down with an unhealthy dose of java kool-aid.
so, after deciding that being able to handle 4000 transactions a minute (when we only get 3000 a day) probably wouldn't be a sufficient answer, this morning I took a moment to analyze my smallish system in ways that would matter to me if I were an (unbiased) VP:
- 14 OO classes (with inheritance, etc)
- 7645 lines of (well commented) code
- 3687 lines of documentation (real pod, not including above comments)
- 654 tests (that have saved me more than once)
I'd wager that the test suite alone makes it the most optimal piece of software in the company, but I don't think that's what he meant :)