HP3000-L Archives

September 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"F. Alfredo Rego" <[log in to unmask]>
Reply To:
F. Alfredo Rego
Date:
Mon, 25 Sep 2000 12:26:27 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (74 lines)
At 8:29 AM -0600 9/22/00, I wrote:

>John Johnson <[log in to unmask]> wrote:
>
>>I've been reading this seemingly ambiguous term everywhere for quite some
>>time and am unable to settle on a definitive explanation of what a "legacy"
>>application is.
>>
>>Is a legacy application one that existed before a certain chronological
>>cutoff point ?  Am I a legacy programmer ?
>>If I write code on the same system, in much the same manner,
>>as those that did before the "cutoff point" should I modify
>>my resume to duly note that I am indeed well versed in coding
>>legacy apps ?
>>
>>And if I can code in "legacy" and "non-legacy" languages, so
>>to speak, am I then bi-lingual ?  :)
>
>For a fun historical perspective, read a legacy paper from 1992:
>http://www.adager.com/TechnicalPapersHTML/YearOfThePies.html
>
>As a bonus, you also get to add some serious questions to your arsenal that,
>to the best of my knowledge, have not been answered satisfactorily after all
>these years.

I got a private message whose creator authorized me to share it with
HP3000-L under the condition that the author must remain anonymous.  The
most telling remark is, "I'm sorry that I can't sign my feelings as the
senior  management here would go ballistic..."

Does this ring any bells?  Anyhow, here is the message:

__________________________________________________________________________

I went back and re-read your "Year of the Pies" paper.  It hit home when
one considers changing ERP systems, i.e. MANMAN to SAP, PeopleSoft, or
J.D.Edwards.  All three of these products require immense manpower from
specialized programming skills, database administrators, "basis
administrators", specialized job scheduling, and system administrators.
This does not include the large number of specialized "consultants" and
the large amount of hardware necessary to implement.  Too bad many
managers view the latest and greatest without looking at what's under the
table-cloth.

I call this phenomenon, "managing by trade journal".  I feel I belong with
answer number 3.
__________________________________________________________________________


So, there it is, directly from the trenches.


Have you re-read "The Year of the Pies"?  I just re-read it and I became
hungry.  I'll take my wife Leslie (the editor of that paper) to a healthy
lunch in town.


Buen provecho,


--

  _______________
|               |
|               |
|            r  |  Alfredo                     [log in to unmask]
|          e    |                           http://www.adager.com
|        g      |  F. Alfredo Rego
|      a        |  Manager, R & D Labs
|    d          |  Adager Corporation
|  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
|               |
|_______________|

ATOM RSS1 RSS2