I think 50% of the quality of a tech book is in the index and the table of contents (in that order). If I can't find it in the index, it may as well not exist in the book -- I'm certainly not going to spend an hour proving the index is correct.
I've ranted elsewhere about specific things not being in the Camel index, which turns out were mentioned in the text. I'm not picking on that one, many are like that. In fact, like anything else, there are very few "great" indices.
After I had the basic syntax worked out, things like Effective Perl Programming took me further than any reference book. Though I've settled on the Camel book to look up functions. But I would have really liked a printed, indexed version of perldoc in the early days. Now, online access is much more prevalent, so it's not a hardship to go looking. But when I'm stuck in a DOS screen trying to read perldoc perlop...well, don't go there, I'm still annoyed with it.
-QM
--
Quantum Mechanics: The dreams stuff is made of
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.