Actually it's not just large teams that it doesn't work well for. Often it doesn't work well for teams of one either.
One good reason for using a version control system even when you are the sole developer and user is that it records the change history including meaningful check in comments. That means there is no need to clutter the code with comments that explain the evolutionary steps that brought the code into the current state.
Even for a single developer having a version control system and making fairly regular check ins provides a nice warm comfortable feeling when you are about to wreck havoc in the code, or have just made a bigger mess than intended.
Perl is environmentally friendly - it saves trees
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||