>Secondly, want to understand *everything*. Even if you leave some parts
>until later because they're less interesting or less relevant, strive to
>understand an entire process from top to bottom. It's amazing how often
I agree wholeheartedly with this statement. I've done the gambit of
advanced perl programming, but I still read perl tutorials and beginner
columns. Why? Because I don't doubt that the author can shed a pe[a]rl of
light in a slightly different way, or highlight a metaphor that I can
reiterate to another...
When I buy magazines, I read *every single bit* of text. Same with books.
It was written for a reason - it's my reading of that text that gives it
reason, not hastily skipping over it because it's uninteresting at the time.
There are some people who say they only read the stuff they need to know at
the time they need to know it - and that anything else means shoving
useless facts into the brain that could push worthwhile facts out. I don't
agree, not in the least.
>Thirdly, devour good examples of code that are just within or just beyond
>your current understanding. They'll both broaden and deepen your expertise
Definitely agreeable. I learn much faster from examples.
Morbus Iff
.sig on other machine.
http://www.disobey.com/
http://www.gamegrene.com/
