I've realized that, with all the software I've written, all the cool experiments I've conducted with programming, and all the libraries I've ever spun together to "get the job done", I only have 3 CPAN modules. Three! Count 'em. One...Two...Three. Not much to show for 7 years of Perl development, eh? I must admit that most of my code during the first 4 years really stunk, the other 3 could probably have been better spent on module development, rather than the odd one-off.
Oh well, here's to a belated new-year's resolution: I'm going to work on more CPAN modules, either in fixing (and probably adding) bugs, adding features, or creating new modules that need creating.
Three be me (Score:1)
Not inadequate (Score:1)
Essentially I have a few unfinished modules lying around. My most ambitious project was probably porting the Aalib to Perl. I was mostly done with it (ev
Re:Not inadequate (Score:1)
Basically, I'm not spinning out CPAN modules for the hell of it; I can't tolerate "Hero Coding". On the other hand though, my modules were very small and, to me, seemingly inconsequential ones. Maintaining them has been very easy, mainly because there isn't much to go wrong.
My original intention of this journal entry was to say that most of the code I've written could have been abstracted to a CPAN module, but w
-man Michael A Nachbaur