Leudwinus, I agree with you; "learning by doing" is the only way to become a programmer. I wrote a blog post on "The Best Programming Language". It was about finding the best language for an individual; we have different problem sets to solve and different brains to solve them with. "The Best Language" for each of us is the one that inspires us to code more, so that we learn more.

There are really two questions that have to be dealt with when we approach a new language. You hit on the first one; "How do I learn?" I tend to read a chapter of a book, and they write very small toy programs. How do I build a hash? How do I change a value in it? Later on I look at how to merge two hashes or call them by reference. When I get going, I'll start a personal project to accomplish something that is important to me. That pushes me to learn more and to keep programming. The code will be pretty ugly and need a lot of work, but it is a learning tool.

My list helps with the second question, "What do I learn?" I often try to take on things I just cannot comprehend. Breaking down the basics into a list lets me focus on learning those basics, one at a time. I can then go back to the big problem better prepared.

In reply to Re^2: RFC: Perl Learning Plan by Leitz
in thread RFC: Perl Learning Plan by Leitz

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.