I used the below books to understand the language and started to solve problems using perl.
Learning Perl, Intermediate Perl, Programming perl and advanced programming in perl(1st edition)
see book reviews section in perlmonks for the above books.(use search facility)
Why do you want to do certifications?. Is it your ambition or just wanted to do because it gives you recognition in-front of your employer?. I am just curious to know.
Because I too initially felt like doing a certification, but later I did only self-learning with the above books, along with help of this perlmonks.org. (my intention is not to discourage/divert you from pursuing certifications).
Now I am feeling confident enough to solve real time problems(and I am solving it in my company).
since you are new to perl, I stop here. waiting for updates from you.
Vivek
-- In accordance with the prarabdha of each, the One whose function it is to ordain makes each to act. What will not happen will never happen, whatever effort one may put forth. And what will happen will not fail to happen, however much one may seek to prevent it. This is certain. The part of wisdom therefore is to stay quiet.
| [reply] |
There are repeated arguments in the Perl community about whether to have any kind of official certification program. So far the decision has come down against it repeatedly for fear that said certification will not be effective for much more than making money for the certifying organization.
See, for example, the discussion at Perl Certification revisited. | [reply] |
If you want to pass some certification test in view of getting hired, you better check what kind of certification will be acceptable to your future employer. Personally I would never hire someone only on the strength of a certificate issued by some commercial organisation who stands to gain more by selling certificates than by being strict.
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
| [reply] |
