Reading various reviews on the book, the title that the author (Tate) has chosen for his book is a bit misleading. On the surface, it seems that he's going to pick a fight with Java devotees and therefore side with sacred truths upheld in this monastery. However, in reality, this book is
devoted to uncovering antipatterns , a term Tate uses because it plays off the way that Sun offered Java patterns to help programmers use the new tools efficiently. Most of the chapters show the wrong way to build something and then show how to correct it.
I haven't read the book to be able to render any conclusive judgement, but from the quote
ignatz submitted here, I seem to believe that the author is still a little short sighted when it comes to Perl. I take his assertion that
most Perl programms
are not well organized as a little absurd and inaccurate. Of course there is some newbie code going around; however, this should not drop shadow over zillions of other Perl scripts that are designed well. After all, any programming language you look at has its set of problems and followers to exacerbate them by writing sluggish code! My recent post
"Confessional: why I wrote bad Perl code" speaks to the same affect. ;-)
His study of
anti-patterns must be quite interesting, however. I would especially appreciate similar subjects brought up in relation to the Perl language.
_____________________
$"=q;grep;;$,=q"grep";for(`find . -name ".saves*~"`){s;$/;;;/(.*-(\d+)
+-.*)$/;$_=["ps -e -o pid | "," $2 | "," -v "," "]`@$_`?{print"
++ $1"}:{print"- $1"}&&`rm $1`;print"\n";}