Re: GO TO HELL.
- From: "Michael Mattias" <mmattias@xxxxxxxxxxxxxx>
- Date: Tue, 22 May 2007 12:13:55 -0500
"Howard Brazee" <howard@xxxxxxxxxx> wrote in message
news:4m865318rmdlddnhf7vj8u8b4bq4mmg65b@xxxxxxxxxx
And if you're more than a programmer, with an interest in your
company's bottom line, you need to evaluate alternatives to
maintaining such code and make appropriate recommendations.
Of course, often your best recommendation is "It would cost too much
in the short run to re-write this now".
I wonder how many times that particular "cost-benefit" analysis turned out
valid in the short term, but way, way incorrect in the LONG TERM?
MCM
.
- Follow-Ups:
- Re: GO TO HELL.
- From: Howard Brazee
- Re: GO TO HELL.
- References:
- Re: GO TO HELL.
- From: Pete Dashwood
- Re: GO TO HELL.
- From: Clark F Morris
- Re: GO TO HELL.
- From: Pete Dashwood
- Re: GO TO HELL.
- From: Louis Krupp
- Re: GO TO HELL.
- From: Howard Brazee
- Re: GO TO HELL.
- Prev by Date: Re: GO TO HELL.
- Next by Date: Re: GO TO HELL.
- Previous by thread: Re: GO TO HELL.
- Next by thread: Re: GO TO HELL.
- Index(es):
Relevant Pages
|