I write unit tests first. Since I know what the code must do, it's easy to write tests that will verify that it does exactly that.
I'm not a good enough programmer yet that the code and the tests are always completely accurate with regards to what must be done, but if the test fails after I've written the code, I know something's definitely wrong.
It's a lot faster, too, especially when adding a new feature.
Chalk that up to debugging avoidance -- planning ahead and proving your code correct is how I reduce debugging time. (It's especially nice if you can whittle down the error to the last two lines of code you added.)
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:
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||