|This kid finished the project in record time but me and this other person would be maintaining it (the web person for the web aspect and me for the programming aspect), anyway this other person was skeptical because some of it was in .Net and some of it was in .asp and she didn't like that there wasn't any comments anywhere?
Now you got me going -- I feel your pain as well. If I don't like rubber-stamp reviews, I really don't like it when management brings in "free" help. Any monkey can be really productive writing code with no design, comments, etc since banging out code is about 25% of what you need to do (if that). The project I mentioned in my previous post also had a case like this. They decided to let some folks half way around the world update a major server. These apes inserted comments in a foreign langauge, had huge indented sections of code with gargantuan variable names, bad memory leaks, and they just dropped it and the abyssmal documentation in our laps to support.
Now that I think about it, I think my life mirrors Dilbert...
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:
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||