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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|