"rac...@anl.gov" <rac...@anl.gov> writes:
> Esther Schindler made the following keystrokes: >> Why hadn't they upgraded or changed, in all that time? >> >> "If it works don't fix it" makes sense for a while. But then you slide >> down the other side of the adoption curve -- especially when it's part >> of your infrastructure or the company really depends on it. That poor >> guy with the Novell servers knew he couldn't get any kind of modern >> software to back up those systems. > > A long time ago, in a machine room that should have been in a > galaxy far far away.. [snip] Well written amigo, I suspect you know very much how that same or very similar example is manifested in many other large companies. Just substitute machine names and "accounting" package. > That was many years ago, but a real good example of if it's not broke... A slight nuance but I look at it a little differently. It's not that it's not broke, it's that it's just a *little* broke. Management wants the least painful, least risky "fix". And for some low value of risky, we delivered that fix. Management usually doesn't have *any* incentive to expend resources on a fix that has to work a year from now, only incentives for sufficient resources to get past the current "event", i.e., port off of dying machine, OS End of Life, etc. In my 30+ year career, I never once saw a manager prioritize a long term fix over a current year fix. The former are usually called,"somebody else's problem, I won't be around". _______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
