I am speaking from very little experience here, as I have never worked on a perl project with another person - always solo

However, I think that every project (be it perl, or one of the more business type projects) needs a plan in order to succeed. Included in the plan should be guidelines as to what is accepted for the results you are trying to get.

Did that make any sense? I think not, let me try to explain further. On a non-code type project (and no I am not a project-manager) there is always a set goal. In order to achieve this goal with the best possible results, there must be a plan put in place. In that plan, there are often rules included - such as when expenses need to be handed in (weekly, monthly, end of project), and when documentation is expected by. Often, there is a template so that all the documentation for each portion of what each team member is working on looks and feels the same. These are just guidelines that I have come across in my non-code projects.

I feel that the same concepts can be applied to code type projects as well. There need to be guidelines, for example, any web stuff, we use CGI, we don't use Lingua::Romana::Perligata, we comment all subroutines with an explanation etc.. If the guidelines are well enough defined at the start of the project, the code should be "standard" enough in the group that anybody can look and see what the other person is doing. This is probably especially important for a large coding effort.

In this method, I think that the freedom of perl will be somewhat negated by the restrictions placed on the project, in this case, that's not a bad thing at all.

In reply to Re: TIMTOWTDI, but enough rope to hang yourself? by the_slycer
in thread TIMTOWTDI, but enough rope to hang yourself? by pmas

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.