Your license to criticize the developer's role in this depends entirely on the requirements you provided him/her with for this project. Were they formalized and agreed upon? Were they clearly presented and sufficiently comprehensive? Sadly, I think all too often developers get the bad press when poor requirements gathering is, in fact, to blame. It is somewhat sad how meticulous one must be when presenting development guildelines, but not doing so will bite you in the end. So, my advice...if the requirements were clear, a stern rebuke is in order...if not, perhaps a process revamp.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||