In my environment (a not-for-profit hospital), it's rare that the spec is clear and easy to write and the programming is hard. More often it's the other way around, or they are both hard. Worse, as is the way with software, either the spec or the programming looks easy at the beginning and becomes hard. Thus it's fairly rare to have a task where a fixed cost, known up-front, is a workable way to do business.
Also, when I do have a task that's that clear and contained, it's often a treat to have something so straightforward to work on; so it's better to to let someone in-house have the benefit of doing it, if possible.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||