Okay. Apology gladly accepted. And I'm happy that it wasn't a personal attack, but only unintentionally read that way.
As for the issue of PBP being a mandatory purchase, I certainly agree with you that it shouldn't be. I think you would get your money's worth even if you only read it once1, and I think coding teams are going to get ongoing benefits from it2, but as I suggest in the introduction: this kind of advice is only useful and productive when the reader genuinely wants it, and genuinely wants to change their coding behaviours for the better. Imposing any coding standard (or even just good advice) on an unwilling or uninterested programmer is almost always counterproductive.
1For advanced programmers like yourself the main benefit isn't the specific development techniques the book suggests but, rather, the philosophical and pragmatic coding issues it encourages you to think about.
2If nothing else, from a reduction in the number of pointless stylistic arguments ;-)
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||