Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

What everyone else is saying. Getting involved in a dev group can be a big growth catalyst too. Peer pressure and publicly viewed code (the code we write for others tends to be a lot better than that we write for our own projects; for me anyway) is a great way to learn. Moose community? Catalyst? Rose? DBIC?

Another excellent tactic for learning is to switch gears entirely. Try Ruby, Java, electronics projects... I found that working with Ajax and JavaScript changed my understanding of CGI/HTTP pretty dramatically even though I'd been doing CGI for years. Rooted out all the weak spots in my competencies. Slinging X(HT)?ML only became natural to me after learning to sling the DOM from JS.

After picking up any new technology you will find your Perl view improves. There are many interesting problem spaces being actively worked on. Social network stuff, distributed data, de-centralized security...

Another big winner is to pick up an abandoned CPAN module. Or start a new one for something like a new web service no one has had time to do yet. Forces you to learn deeper topics like testing and distribution.

Diving into the books can be nice -- I own just about all of them; some in multiple editions at this point -- but I find that I only absorb the stuff well when I can apply it to a problem space.


In reply to Re: Finding the path by Your Mother
in thread Finding the path by Spidy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (3)
As of 2024-04-16 18:37 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found