Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
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 do. It's almost cheating. But why not both write modules and deploy them? You're the author and the implementer. You wear two hats. Half of the time, you're concerned about the general problem as it applies to everyone or most people (reusable code); the other half the time, you're working on the suber sekret company specific business logic (deployment).

    Without rationalizing it, I've done this, and other people in the company have before me. And it makes sense to minimize how much business specific business logic is in the code as this stuff changes. A lot.

    This company has a "we own the code you write while you're on the clock" contract, which is a hell of a lot better than "we own all the code you write while you work here". I'm finding myself not invoicing for a lot of hours because I spent those hours working on a CPAN module. I don't think I can ween myself off of this. I think I have to stay contract. Or, more correctly, they need to offer me a bridge to this dicotomy if they want to take me perm.

    So, it'll be interesting to see how this plays out. I'm taking a strong position for module based development. Will they accept and embrace it? Will they make it worth my while? Or will we just be at odds over it?

    -scott
    • 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