I had to exercise due diligence to design and implement the code right as it had to run for at least a full-week non-stop to complete the job.
An entire week? That doesn't sound right. Are you sure Perl was the best choice for the job? Could an extra couple hours of optimizing have saved a couple days of execution time?
Is it reasonable to turn away such requests or pursue them with vigor?
Just make sure they know the disadvantages. Security, reliability, maintainability, and many other things are reduced by rushed development. Sometimes it's worth it, sometimes it's not.
-
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.
|
