comment on

And that knowledge is very likely to pay off in spades one day.

Agreed. "Tranparency or performance, pick one" only bothers me occasionally since I don't usually care about performace much anymore. When it does bother me, it bites hard. Back when I was using C a lot I found I would try to think ahead about potential problems like this. Now that I use Perl, I find I get lulled by the "good laziness" it fosters and start incorporating some of my own "bad laziness" (i.e. not thinking at all)...

In reply to Re: Bitten by the worst case (or why it pays to know whats inside the black box) by bluto
in thread Bitten by the worst case (or why it pays to know whats inside the black box) by demerphq

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.


Your skill will accomplish what the force of many cannot
	PerlMonks