What did we gain by spending the extra week?
Let me see : 2 weeks build time for 15 minutes run time, or one week build time for one hour run time.
What is gained by spending another week optimizing ?
More time for the backups that run after/before the process.
More flexibility for the administrator, secure in the knowledge that an important business process can be rescheduled without severely impacting the nightly run schedule.
The code taking one hour to complete will be judged obsolete sooner because of time constraints, whereas the 15-minute code will be able to justify its usefulness longer, since it will allow for more tasks to run in the same night.
The price of the box is irrelevant, there has to be a box anyway. The cost of the coder(s) is relevant, but that justs pushes back the date at which the code can be deemed to provide value for money (however the company decides to calculate that date).
I agree that quick & dirty is sometimes an acceptable way of doing things. Unfortunately, quick & dirty is what gave us buffer overflows in the first place. And cut&paste code is what has kept them alive.
My opinion is that it always pays to carefully plan an application, and design it as best as is possible - even if it is not destined to support a critical business process.
Pascal.