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.

doing without a TARDIS 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • split site development of the same codebase

    Wouldn't that fairly accurately describe a project such as ... I don't know ... Perl!?!

    I believe you have some familiarity with how that works :-)

    I'd have thought that in a commercial project, the main difference would be that a project manager would be able to step in and "make a call" in the case of conflict or disagrement.

    • From my experience in working with Perl is that being several timezones apart from the others can be a bit of a challenge at times. At least with open source, people are generally available. At work, people tend to be available only during the eight to ten hours they are expected to be there. So, if your separated by eight hours or more, you may never reach some people in the office ever. That's where I guessing where the challenge comes in.

      • You've expressed the distinction better than I was going to. In my experience volunteer developed open source (seems) to be different and therefore easier for a couple of reasons:

        • People are generally available for more hours, so lack of overlap is not such a problem
        • People are generally working on individual subsections of the code, so don't conflict (and so don't need communication to resolve that)
        • People are generally not working full time, so the sheer pace of development is slower. (Or at least, the attempted pace)
        • People are working on what they feel like, or what they feel is important, so if they realise that they're about to start creating conflicts with someone else, they back off and wait. There's no business pressure to have both projects done soon and simultaneously

        I think that if Perl attempted to have development done full time by multiple people in mutliple locations, it would rapidly grind to a halt as everyone spent a lot of of their time communicating to avoid conflicts, or liasing to ensure that parallel development stayed in touch. So I feel my original questions remain unaswered.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.