In my oppinion, the larger your code is, the more places for it to fail.
I know that describing exceptions takes time - even more than to write 'working' solution, but... if something fails, you should be able to find (immediatelly) what, where and when has failed. Whenever possible I check return codes of functions and calls and log all errors to a file/syslog/whatever. During developement you can log every single error, eg. missing parameters, etc. (of course for developement you don't use any sensitive data). On working systems you should log all exceptions and failures
, where 'all' means enough for you to know exactly what failed, but not enough for others do compromise data your software is work with
BTW. Another rule says that the less you know, the better you sleep
but that doesn't apply to programmers ;-)
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||