Re: What's the most important thing to learn in the Perl world?

I would have to say - find real world problems to solve. Then apply your existing Perl skill set to solve them. Soon you'll realize you could do them better, or faster, or lazier. Then its time to upgrade your skill set.

Most people are happy with reading the best of books, but if you can't apply that knowledge then it withers away.

Give up your day job! Go find some real life threatening problems! :-)

--
arc_of_descent

Comment on Re: What's the most important thing to learn in the Perl world?

Replies are listed 'Best First'.
Re^2: What's the most important thing to learn in the Perl world? by insaniac (Friar) on May 11, 2005 at 14:38 UTC
in my opinion: you gave the only suitable answer. Find Real World Problems (to solve). I've learned that I always buy books when I don't need them (but I do want to learn about it..), and usually I don't read them (at that time). Or, if I do read them right after I buy them, it seems I don't fully understand them, or the books seems too difficult. If for instance months later I get a project assigned where I need to apply for instance the knowlegde I couldn't grasp before... at the end of the project I feel immensly enlightened (of course after reading the book). Because: * I really understand most parts of the book I bought months ago * I truely feel I've evolved (because my code 'looks' better) * All code I wrote before the project looks yukkie ;-) (but that's just my personal experience) so arc_of_descent++ ! And to all you book loving junkies: start looking for problems! first try to solve them in a way that's not too difficult for you (to understand). And after that: try to improve your script ;-) to ask a question is a moment of shame to remain ignorant is a lifelong shame	[reply]

Replies are listed 'Best First'.

Re^2: What's the most important thing to learn in the Perl world?
by insaniac (Friar) on May 11, 2005 at 14:38 UTC

If for instance months later I get a project assigned where I need to apply for instance the knowlegde I couldn't grasp before... at the end of the project I feel immensly enlightened (of course after reading the book). Because:
* I really understand most parts of the book I bought months ago
* I truely feel I've evolved (because my code 'looks' better)
* All code I wrote before the project looks yukkie ;-) (but that's just my personal experience)

so arc_of_descent++ !

And to all you book loving junkies: start looking for problems! first try to solve them in a way that's not too difficult for you (to understand). And after that: try to improve your script ;-)

to ask a question is a moment of shame
to remain ignorant is a lifelong shame

[reply]