Welcome to the idea of lifelong learning. I try to read a new book on programming every 2-3 months, in addition to what I gather from here, reading over CPAN source code, code and design walkthroughs at work, and discussions with friends.
Sounds like a lot of work, doesn't it? Well, if you don't truly love programming, it is a lot of work. But, that's what you need to do in order to stay at the top of your game. If you do truly love it, it's not work - it's fun. Call me a geek, but I think it's fun to read Perl and XML while eating pizza (if I'm by myself).
(If you don't truly love what you're doing, stop and go do something you do truly love. That's just plain good life-advice.)
------
We are the carpenters and bricklayers of the Information Age. Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement. Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified. | [reply] |
The camel book may be long but most of it is reference. If you can make it through the subroutines chapter, you've covered less than a quarter of the book but that should get you to the point where you can write some very useful programs. Write some programs for a while to get used to perl. Then go back to the book and start working on the next few chapters, one at a time. By the time you hit page 400, you've covered all of perl. The rest of the book can be viewed as best practices, style guides and reference.
---
print map { my ($m)=1<<hex($_)&11?' ':'';
$m.=substr('AHJPacehklnorstu',hex($_),1) }
split //,'2fde0abe76c36c914586c';
| [reply]
[d/l] |