in reply to What's on your Bookshelf (related to perl)?

I'm not a book freak at all. My main source of information is searchable references, like perldoc. This makes my Perl book list a rather short one. Until very recently, I owned no Perl book at all. But now, I own:

Besides the subject of Perl, the only recent computer books I have are I haven't read MRE's 2nd yet, though.

Some books I read via O'Reilly's Safari. I thought that that'd be cheaper than buying them if you read them only once, but this only works if you remember to actually use your membership. I haven't used it for months :)

I'd probably use Safari much more often if its interface didn't suck, and they fixed that stupid bug that makes == render as =  =. I wanted Safari to be able to read books on my PDA. I scraped some (against their rules, so don't do this) in order to be able to do so. Now, they provide downloads. Single chapter downloads, which is pointless for someone who mostly skims.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

Replies are listed 'Best First'.
Re^2: What's on your Bookshelf (related to perl)?
by perrin (Chancellor) on May 17, 2005 at 00:47 UTC
    Perl Medic a disappointment? How so?
[reply]

      Perl Medic a disappointment? How so?

      It doesn't quite deliver on its cover promises. Perl Medic is a good book that I would recommend to friends learning Perl, but I fail to see how it's really to do with the medic part. The part in the beginning of the book, about politics around programming in the professional world, is very valuable information one doesn't read in other places. The rest of the book appears to be written for beginning programmers, who in my opinion will benefit from a book like Beginning Perl.

      I expected an advanced level book, written to help maintaining awkward legacy code. The text on the cover fortified that expectation. I also expected more examples of what one will encounter. Simple things like how for (@_) { ... } in older versions of Perl didn't check if something was read only, and that you can often fix this by simply copying the array, like so: for (my @copy = @_) { ... }. It doesn't have enough of that kind of Perl-specific advice, that is necessary to effectively deal with old and broken code you inherit.

      Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

[reply]
[d/l]
[select]
        Okay, if that's what you were expecting I could see why you would be disappointed. I agree that the book is only marginally about legacy code.

        What I like about it is that it's the best book I've seen about writing high-quality maintainable perl. It's not an "advanced" book in terms of teaching tricks and sneaky techniques, but rather just the opposite -- it's about doing things right.

        I would also agree that there was hardly anything in this book that I didn't mostly know already at this point, but what's great about it is that it puts all of the advice that I normally give to co-workers -- write tests, use perltidy, use templates for web apps, etc. -- in one place. I wish every perl programmer would read this book.

[reply]

In Section Meditations