“Testing” in Perl is an especially poignant example of TMTOWTDI. A search of CPAN on the word, “test,” produced 5000 hits, and a search of module-names beginning with Test:: has 806 entries today.
What has become absolutely clear to me is that, “punching a few buttons” and from that saying, “okey, it seems to work...” isn't enough. Also, “you really don't know ‘your own’ code!”
No... the only way to test, is to do so very explicitly and continuously.
When you start doing this aggressively, you realize just how unstable code that you believed to be “production ready” actually was, all this time. (And that's a very sobering thing to realize about your profession.)
But when you start building things out of code that is being aggressively tested while you build it, and/or you start flushing-out the problems in production code before users have a chance to find them, you start “waking up in the night” much less often.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||