So, I have a couple of confessions to make:
- I confess that sometimes I am a little judgemental of others code
- I confess that I am defensive when other people judge my code
- When I first looked at my assigned module, I confess that I started passing judgement on it.
- When I first started really digging into my assigned module, I confess that I seriously considered recommending that it be deprecated.
- I confess that I was absolutely wrong, and that in being a judgemental ass I almost missed the whole point of this exercise.
Neil did not ask me to be judgemental, or to critique other peoples’ contributions to the rich set of modules contributed freely to CPAN. Neil’s challenge wasn’t for us to help identify modules to remove from CPAN, I suspect that there are already parameters for doing that and that when it is appropriate to do so that this is done.
The challenge at hand was to take a module that has been abandoned and left lonely, not being updated or added to, and give it a little TLC. Even if it is just a spit-shine, these modules need something… anything.
I can’t help but feel like I walked into this challenge having completely missed the point of the whole thing.
It’s hard releasing stuff into open source. I’ve been doing so for more than 18 years now, and it’s not an easy thing to do, subjecting your work to criticism. We owe it to one another to at the very least not be judgemental and dismissive in this challenge.
So, what am I doing to improve
App::CLI::Extension? I’ve got two things in store:
- First, this module doesn’t currently build. I think it’s a change in
Module::Installthat’s causing trouble, so I want to fix that.
- Second, I want to improve the module to meet more of the current best-practices. I’ll probably use a lot of
perlcriticand PBP for this.
I don’t know what else to do just yet, but it seems like so far I’ve got a few hours of work. Let me know what you think, and if you use this module, definitely speak up and let me know if you have any specific requests.