Re^5: Module Bloat and the Best Solution

I don't think it's such a ridiculous re-statement at all actually. Unless there is a way for a normal perl developer to know in advance what code is battle tested and what code has just been put up, you aren't giving the perl community much to base their decisions on. Sure, you have your reasons for using List::MoreUtils (even though it isn't available on the production boxes in my environment) because you feel it's rock-solid code you are willing to stake your reputation on.

So I propose the question again: I'm a developer. I need to do some task in perl. When should I be hitting CPAN as opposed to just writing the few lines myself? What criteria should I use to know when to use CPAN and when not to? Furthermore, just be virtue of being in CPAN doesn't mean I necessarily want to stake my reputation on it. So what criteria do you use to know when you can stake your reputation on a CPAN module?

--
I used to drive a Heisenbergmobile, but every time I looked at the speedometer, I got lost.

Comment on Re^5: Module Bloat and the Best Solution

Replies are listed 'Best First'.
Re^6: Module Bloat and the Best Solution by dragonchild (Archbishop) on Nov 12, 2007 at 18:36 UTC
By doing the same thing that you do with every other decision about a product you make in your life (both professional and personal) - you ask people you trust for their opinion. As far as when you should use CPAN - I always look on CPAN first and ask around whenever I run into something that requires some thought. Now, I have a really good idea of what's on CPAN when it comes to the kind of work I do and I know the people who work on it. Just like anything else in life, you should know who's building the stuff you depend on. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]

Replies are listed 'Best First'.

Re^6: Module Bloat and the Best Solution
by dragonchild (Archbishop) on Nov 12, 2007 at 18:36 UTC

As far as when you should use CPAN - I always look on CPAN first and ask around whenever I run into something that requires some thought. Now, I have a really good idea of what's on CPAN when it comes to the kind of work I do and I know the people who work on it. Just like anything else in life, you should know who's building the stuff you depend on.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

[reply]