|
Get what you pay for is right... This company tried going from S/36 to a package on an ADP system because subsidiary manufacturer did OK on it. No fit, but they sold them the system. After a few months they gave up and went to a package on the AS/400, still here.. VP says he learned his lesson good. They were checking on software for a Y2K change, but finally decided to adapt what they had to Y2K (yep, some 150 files, 700+ programs). My predecessor checked a couple of packages on NT. One NT vendor kept bragging about how fast their programs came back up, and how clean they were after "unplanned outages". They bragged so much she asked 'em "Well, how often does your system go down?" They said, "Well, before we tweaked our system it was average once or twice a day, now we've got it down to max two times a week". Can they afford to run a company like that.?.. - Alan alan@xmiami.com ----- Original Message ----- From: <Terry.Rhoades@blum.com> To: <MIDRANGE-L@midrange.com> Sent: Monday, January 29, 2001 4:37 PM Subject: Re: New names > > Bill, > > You should have told the interviewer that the old saying, "You get, what you pay for." applies to IT personnel too! > > Regards, > Terry > > > > > > "Bill Meecham" > <bmeecham@weichertrea To: <MIDRANGE-L@midrange.com> > ltors.net> cc: > Sent by: Subject: Re: New names > owner-midrange-l@midr > ange.com > > > 01/29/01 02:51 PM > Please respond to > MIDRANGE-L > > > > > > One key item is that it's not a Legacy system! No one wants a legacy. > Something like that just has to be way past it normal expected life-cycle, > it's a legacy! Isn't that what had to be updated for Y2K, wasn't it that > legacy stuff that caused all of the problems? IMHDAO, if an application > does not run on a legacy system then it's already a greater application than > one that does. Imagine trying to find legacy personal to maintain the code > and hardware! They've got to be older and more expensive and out sick for > Rogaine therapy and Viagra treatments all the time. I can hire kids that > eat and breath this PC stuff, pay them a fraction of a legacy coder $ and > they'll live at the office, do what I tell them to do and won't complain > about anything. Heck I can hire an army of kids to do this work instead of > gray-haired people like you. > > </devil's advocate> > > The last 3 sentences are paraphrases of what I was told at an interview that > I went to in late August. > > > > > > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > > > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.