Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Tuesday June 14, 2005
05:05 PM

Tech Reviewers for the new Alpaca

[ #25202 ]

Randal, Tom, and I are gearing up for the second edition of the Alpaca, which we are going to re-title "Intermediate Perl". Just like we did with the Llama Fourth Edition (now finishing QC1 and on track to be at OSCON), we're looking for tech reviewers and masochists you want to tell us where we made mistakes, what we left out, and so on. You can write to me directly (, leave a note here, or show up at a special geo-cache Randal set up in the Brazilian rainforest (write to me for the coordinates).

In the last tech edit, I included a lot of Perl newbies so I could get beginners comments on Learning Perl. This time I'm looking for people who pretty much already know the stuff in the Alpaca and also know what's happened in the three years since it was first published.

Typically these things are a volunteer edit, but if you catch up with one of us at a conference we'll buy you drinks, etc.

Need need to waste your time writing, dha, since I've already volunteered you. :)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I'm interested in reviewing the book.
  • [The] second edition of the Alpaca ... we are going to re-title "Intermediate Perl".

    I'm quite amazed at the independent evolution of different Perl training houses to similar course names and content. Our course has been called Intermediate Perl [] for years. However while it covers packages, references and modules, we've split the object oriented material out into a separate course []. The only trouble with that is convincing businesses that a knowledge of OO Perl is worthwhile.

    We do have a noticable

  • in case you think I can be a good reviewer (as you had some experience before with my comments).
  • I think I've read and coded enough to be helpful.