I suggest staying away from the "Username::*" naming convention. If you decide later you like it well enough to
publish it on CPAN then you'll have to rename it.
Version control systems are useful, and definitely a good idea even on solo projects (I'm a fan of RCS these days, largely because I live inside of emacs... checking something into RCS is just 3 keystrokes: "C-x v v"), but I'm at a loss as to how version control would make it easier to find a module.
I think the original poster really needs better ways of searching his disk... I keep meaning to play with swish-e, myself, but in the meantime I fall back on find/greps of various sorts.
Of course, a better organizational strategy wouldn't hurt, but there really isn't any one right way of doing these things...
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.