I stared at Him for a good fifteen seconds. Then I got up and left the room.
Well done. Many people seem willing to sacrifice what they know are absolute minimum standards in order to get the job "finished". In a previous project I worked on, not just the programmers but also the project management had fallen to this rubber-stamping dark side. In one case
people were left out of a code review, since their (expert) comments would presumably slow things down. I've seen more than one review announced out of the blue for a major piece of code (>10K lines) just a few days before
it occurred. I think the classic case occurred when a review consisted mainly of people that didn't know the language the code was written in, so I'm sure the review went smoothly.
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:
- 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
Outside of code tags, you may need to use entities for some characters:
| |
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.
|
|
