in reply to Learning the Deeper Secrets of Perl

A few thoughts...

Reading and studying only helps to a point. I find fixing, adapting, and building things is a better way for me to expand skills. This improves both developer skills and Perl skills.

Developer skills involve computer science, work habits, planning techniques, and more. Much of this is learned more easily from others than from books.

Perl skills tend to involve specific tasks like file processing, hash manipulation, and data base interation. I find that even when one thinks they know a language well, there tends to always be something else to learn.

  • Comment on Re: Learning the Deeper Secrets of Perl

Replies are listed 'Best First'.
Re^2: Learning the Deeper Secrets of Perl
by radiantmatrix (Parson) on Jan 27, 2005 at 14:36 UTC

    While I would agree with you that learning from others would be best (that's why I hang out at the Monestary to begin with), I work in sort of a Perl Desert. All about me use C# and VB. I also learn *very* well from books, when properly supplemented.

    I learned Perl to begin with by reading Programming Perl (the Learning book was paged through and seemed good, but not presented in a way that works with how I learn) and using what I learned to stagger my way through a few downloaded Perl scripts.1.

    I expect that the way to increase my Perl skill is to read as much theory as possible, then study others' scripts that use that theory, then write my own as well.

    1. From Matt's, originally. I learned more about Perl by identifying the problems with those scripts... then I went to CPAN and a few other Perl-code haunts and worked my way through increasingly complex scripts until I felt I had a working knowledge of them.

    require General::Disclaimer;
    s//2fde04abe76c036c9074586c1/; while(m/(.)/g){print substr(' ,JPacehklnorstu',hex($1),1)}