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.

Bilingual?  That's a good one.  Coincidentally, this paper ends with
"Bon Appetit"
(I removed the diacritical on the "e", for the benefit of Stan's
email client :-)

Always looking forward to the future (which somehow depends on how much work we
do today, because good things tend to NOT fall out of the sky by themselves),
--
  _______________
|               |
|               |
|            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.
|               |
|_______________|