Perlians boast rather proudly about how "there's more than one way to do
it" in Perl. They don't point out that this fact means that there are
lots of ways to write confusing, unreadable spaghetti code in Perl. But
while TMTOWTDI can be a handy aspect of the language, I usually walk
away frustrated because they tend to wave it like a banner rather than
showing me with code specifically what these different ways are and what
the relative merits are to each (eg, extensibility, maintainability,
readability, etc).

Anyway, so I find the premise behind this book intriguing because rather
than blowing TMTOWTDI in my face, it sounds like he's stepping forward
and explaining which ways are best for specific goals.

I'm looking forwarding to reading the book when I get a chance.

Dave