I think of PBP in the same way as strictures. They're great starting points and, in the absence of any better ideas, it's usually good enough to get by. That said, I violate strictures all the time in my code. In very specific places, for very specific reasons. I do the same thing with PBP. I have my own set of best practices that have grown over the past dozen years and 15+ gigs. They're mostly the same as TheDamian
's, but not quite.
That said, I'd much rather a slavish adherence to PBP over a slavish adherence to no best practices (which I see from time to time).
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||