I think about whether the module's going to represent an object, whether it's going to be an API, or whether it's just going to be a collection of useful, related code.
Once I've figured that out, I can start writing the module, ideally writing tests as I go, so that I have some confidence that new stuff doesn't break the old stuff.
The three standard modules I start with are strict, warn and Carp, and I always write code with error-checking in place -- that way I never have to remember to add it later.
And I also use git, committing early and often. I can't tell you how many times way back when I hacked on some code, realized it was a disaster, and longed to go back to an earlier, working version. With git, you can totally do that.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||