There are challenges at different levels. You mention "building infrastructure". Some of the stuff I have enjoyed doing most is of that sort, although more often tool building than library building. It is especially satisfying when everyone on the team uses the result every day and it works so well that it has pretty much disappeared into the woodwork.
Finding elegant solutions to problems of any size. For example, I enjoy challenges related to golf. Not golfing code to obscurity, but golfing it to a point of elegance where it is clean, succinct and clear. Many answers to PerlMonks questions include fragments of that nature. Not always the main part of the answer, but often a clean way of setting up the preconditions for the core part of the answer.
Perl reduces RSI - it saves typing
-
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.
|