comment on

Beware of the dangers of optimizing/removing infrequently run code! Believe me, that can be the most critical stuff and gets hardly ever tested.

A prime example is code that run end-of-year to, let's say, restart invoice numbering with the new years prefix. E.g. switching from 2209543 to 2300001. This particular code runs once a year for *maybe* a tenth of a second. But if it's missing or broken, bad financial things can happen.

That specific example is rather fresh in my mind. Guess what i spend the first week of January fixing while shuffling around on my knees begging the customer for forgiveness.

PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP

In reply to Re: Are there CPAN modules that can help write realtime software catalogs by cavac
in thread Are there CPAN modules that can help write realtime software catalogs by misterperl

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks