Nice, as usual. I'd add that it's not just especially beneficial for new hires. Every shop I've worked, the difference in skills between the top cats and the others was nearly exponential. Not just new hires but guys who were supposed to be experts and had been doing it for a decade or more. The Perl hacker at Amazon I learned the most from was a self-taught guy but he just knew the stuff better than all the rest of us. I think he was embarrassed he didn't have a CS degree too; all the while answering Perl and hardware questions from all the rest of us.
Code review is also a great way to set aside the opinions for the practice. It's easy to say XYZ is how we should do it because someone read a whitepaper but when someone else whips up some ABC instead and shows you how it fits in your app/code-base perfectly it's hard to keep saying, "but, but Sun says XYZ will save us from werewolves... "
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||