comment on

You might consider getting involved in the Phalanx project, which encourages volunteer effort to increase test coverage. You'd get practical experience writing code for tests, as well as getting exposure to how other people approach more complicated problems with Perl.

Otherwise, I'd suggest picking a micro-project that has meaning for you. Write a program to parse a log file, or aggregate RSS feeds, or send you a reminder list for birthdays of your friends and family. If these are too "easy", then step up to more complicated things. Search around your electronic life for things that are repetitive and see if Perl can help you automate them.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: Learning by doing. by xdg
in thread Learning by doing. by Yzzyx

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.