Run a perl style contest.
Pick a coding task, and have a panel of judges rank them on their documentation, code clarity, program structure, and overall performance of thier code (ie. does it do the task assigned, and no more? Does it do it correctly for all cases? Is it testable? Was it tested at all? Did the documentation include the test cases? Is the documentation easy to maintain (eg. literate programming techniques, where the documentation is embeded with the code)?
In short, run a contest on what you want to test: their ability to write "solid, readable code". Use the entries as a talking point for developing better coding style and practices within your department. A lot of the points of style are subjective; but that's entirely the point. You want your developers to understand what kind of code that you expect them to write: giving them examples of what you do and don't like will help much more than saying "just do it, and do it 'right'!"
Just my $0.02
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||