It's difficult for me to get out of the habit of using
whatever tool I've been working with at the moment to solve
any problem that comes up. (Usually, that means C and
Perl.) When I can break out of that rut, though, very good
For instance, a while ago I was handed a fairly nasty
data munging problem (I can't recall the specifics, so this
story may sound pretty vague; my apologies). Naturally, I
first attacked it with Perl. It wasn't responding well to
the attempts I made at solving it, and I was getting pretty
frustrated. In a fit of right-brained brilliance, I
realized that, if I only had the data in a DB, it would
take but one line of SQL to solve the problem. Five
minutes later, I was done.
This is one major advantage to having a reasonably broad
knowledge of the field: other solutions are constantly
bubbling and percolating just behind your subconscious.
Sometimes, they escape; sometimes, they're better than what
you've been hacking on for the last hour.
The hell with paco, vote for Erudil!
/msg me if you downvote this node, please.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.