Ulysses, an acquaintance of mine, left USS unexpectedly and is now working for the county. Not long after he left, another systems programmer, Ulee, needed to update the USS message. He searched all of the primary source files at USS for the USS source, but didn't find it. He then tried looking in the USS user directories and found Ulysses' /u/USS (coincidentially, Ulysses' ID was USS), USS source there, called USSSRC. So he was finally able to update USS's USS message by changing the USS source in USSSRC at /u/USS.
OK. I admit to not knowing Ulysses personally. However, if you successfully followed this message, then you don't need an interpreter to understand what USS means. WOuld it be nice if the same interpretation always applied to the same acronyms? Sure, but then we'd be left to talking about real problems, and that gets boring. Many of the best systems programmers are successful because they demand precision and clarity. Many are successful because they can adapt. Those who are precise and clear in their own work and adapt to the environment around them have the best of both worlds. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
