Productivity vampires? Is that really legacy systems you refer to, or is it just yesteryear's fad that's starting to show its true colors? Some time ago I work

Productivity vampires? Is that really legacy systems you refer to, or is it just yesteryear's fad that's starting to show its true colors? Some time ago I worked on a modern travel reservation system frontend, to replace an aging 5250-based one. When I finally spent a day with the customer's end users to validate some things and learn how they worked (those things never shine through the specs) it was like a punch to the stomach. They were happy to see me and happy for the system replacement, but they worked with such lightning speed in the old system (where all 24 F-keys were bound and known by heart) they could keep up a conversation with the client while contantly pulling out the information they needed. Just reaching for the mouse in that situation would have incurred noticeable latency for the customer. A snowball's chance in the proverbial hell would constitute much better odds than my web based system would have to improve their productivity. I didn't stay on that project until the end (for other reasons) so I don't know how it turned out, but it was my first real encounter with "legacy" systems and it humbled me like nothing since. There are still high cost to maintaining these systems, and their batch-orientedness makes modern always-online mode very difficult. But productivity for end users should be very hard to match, especially since they were built for kilobit lines and megahertz computers in mind.