Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

scrottie (4167)


My email address is Spam me harder! *moan*

Journal of scrottie (4167)

Friday March 30, 2007
03:32 PM

Alias on being a CPAN goon and building from components

[ #32847 ]

Alias replied to my last post with this gem. It was too good to just leave buried in the comments. The "or else..." line was mine, the rest is Alias' reply. Enjoy.

> or else Java goons come in and build the whole site out of componets

Hmm, I'm a CPAN goon that comes in and builds the whole site out of components :)

I keep saying this over and over again, but in the long run I find the only way to create large amounts of functionality over a period of time is by pretending that it's all eventually going to end up on CPAN.

I can skimp on the docs a bit (as long as the POD's there for the primary APIs) and I can skimp on the tests a little if I have suitably thorough empiric-type practical test scripts and become a perfectionist when it comes to regression tests.

But the basic structure of making most or all functionality as a CPAN-like distribution does seem to be the only way I can avoid the debt.

And once I got into that rhythm I've found I can generally found that it's not TOO hard to sell to management that it's better that we build most or all code in reusable "components" so that it can be used by people for other projects.

It takes longer the first time, granted, but there's no second time, and you can maintain development at a reasonable pace indefinitely.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.

  • There. Now that's unburied I can comment on it >=)

    I took a half hearted stab at the black hearts of those quasi-programmers, the increasingly popular sort who only deploy modules.

    You set me right. It's not over-willingness to deploy modules that causes me suspicious for their dedication and management's judgement in hiring them. Deploying modules is a safe route for the reasons you listed. Make the module test itself pretty well and then it's much less unit level testing the whole application has to
    • Well, so far my solution for the second problem (of getting companies to release stuff on CPAN) is basically.

      "If the code is part of our secret sauce we have to keep it secret. If it's NOT, and just general functionality, then by releasing it to the community we get other people to test our code free of charge. And people that find bugs will often fix them for us, and we don't have to pay them for that either!"

      (or situation-specific variations on that theme)

      The second, and frankly easier, part of this is to