I am in *complete* agreement with
tachyon on this. If there's going to be more than 2 people working on this, the modularizing this is very helpful. If this expands to 5 or more, then it's going to be about the only way you can keep your sanity.
Think about your design. Draw out the major modules on paper. Think about the design again. Confer with the other people on the design. Then, delegate control and responsibility. Tell Joe that the Foo subsystem is his and let him oversee it, tell Bob that the Bar one is his, etc. Then you just watch over it all and insure that everything runs smoothly.
Most every large project works this way. The Linux kernel, Mozilla, Gaim, these are just a few that I can name off the top of my head.
/\/\averick
perl -l -e "eval pack('h*','072796e6470272f2c5f2c5166756279636b672');"
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.