How about trying to think of an itch to scratch? There has bound to be some task you always wished to have a tool or module for; something that you sorely miss during your daily work routine, or which would just be handy to have. I can always think of four or five of these, and while they're usually not very complicated to implement, doing so properly with a solid generic interface (whether commandline or API) typically takes a bit of effort. Using downtime to write one of these sounds like a good investment.
Maybe, if that's your inclination, you can even donate it to the world as free opensource software; if you choose to do so however, be sure to check your contract with your employer. It may restrict the rights you have on software written at work or even in your spare time (flashbacks from the tilly incident.. sigh).
Makeshifts last the longest.
-
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.
|