This was the same problem I ran into once upon a time. What I ended up doing was writing modules strictly for myself (that is, not for upload to CPAN) that were little shortcuts for things. Anything that I found myself doing with any regularity at all, I wrote as part of my series of "Kurt" modules. Writing several of these was sort of like grist for the mill. It got me thinking in module writing mode, and then from time to time, an idea for something new would pop up, which would lead to a module that was eventually uploaded to CPAN. You can, I think, apply the same rule to writing perl modules that you are supposed to apply to writing fiction: write about what you know. Write a few simple modules strictly for yourself, and then when the Perl Muse decides to perch upon your shoulder, just sort of run with it from there.
___________________
Kurt
-
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.
|
