Respect Your Elders

"Oh Geez," exclaimed the guy who sits 2 desks from me, "that thing is ancient! Why would they give him that?"

Taking the bait, I popped my head over the wall and asked "what is?"

He showed me a text message, sent to him from a buddyan engineer (EE, actually) who worked for an oil company. My co-worker’s iPhone 6 displayed an image of a laptop we could only describe as “vintage”:


(A Toshiba Tecra 510CDT, which was cutting edge…back in 1997.)

"Wow." I said. "Those were amazing. I worked on a ton of those. They were serious workhorsesyou could practically drop one from a 4 story building and it would still work. I wanted one like nobody's business, but I could never afford it."

"OK, back in the day I'm sure they were great," said my 20-something coworker dismissively. "But what the hell is he going to do with it NOW? Can it even run an OS anymore?"

I realized he was coming from a particular frame of reference that is common to all of us in I.T. Newer is better. Period. With few exceptions (COUGH-Windows M.E.-COUGH), the latest version of somethingbe it hardware or softwareis always a step up from what came before.

While true, it leads to a frame of mind that is patently un-true: a belief that what is old is also irrelevant. Especially for I.T. Professionals, it’s a dangerous line of thought that almost always leads to un-necessary mistakes and avoidable failures.

In fact, ask any I.T. pro who’s been at it for a decade, and you'll hear story after story:

  • When programmers used COBOL, back when dinosaurs roamed the earth, one of the fundamental techniques that were drilled into their heads was, "check your inputs." Thinking about the latest version of exploits, be they an SSLv3 thing like 'Poodle', or a SQL injection, or any of a plethora of web based security problems, the fundamental flaw is the server NOT checking its inputs, for sanity.
  • How about the OSI model? Yes, we all know its required knowledge for many certification exams (and at least one IT joke). But more importantly, it was (and still is) directly relevant to basic network troubleshooting.
  • Nobody needs to know CORBA database structure anymore, right? Except that a major monitoring tool was originally developed on CORBA and that foundation has stuck. Which is why, if you try to create a folder-inside-a-folder more than 3 times, the entire system corrupts. CORBA (one of the original object-oriented databases) could only handle 3 levels of object containership.
  • Powershell can be learned without understanding the Unix/Linux command line concepts. But, it’s sure EASIER to learn if you already know how to pipe ls into grep into awk into awk so that you get a list of just the files you want, sorted by date. That technique (among other Unix/Linux concepts) was one of the original goals of Powershell.
  • Older rev's of industrial motion-control systems used specific pin-outs on the serial port. The new USB-to-Serial cables don't mimic those pin-outs correctly, and trying to upload a program with the new cables will render the entire system useless.

And in fact, that's why my co-worker's buddy was handed one of those venerable Tecra laptops. It had a standard serial port and it was preloaded with the vendor's DOS-based ladder-logic programming utility. Nobody expected it to run Windows 10, but it fulfilled a role that modern hardware simply couldn't have done.

It's an interesting story, but you have to ask: aside from some interesting anecdotes and a few bizarre use-cases, does this have any relevance to our work day-today?

You bet.

We live in a world where servers, storage, and now the network is rushing toward a quantum singularity of virtualization.

And the “old-timers” in the mainframe team are laughing their butts off as they watch us run in circles, inventing new words to describe techniques they learned at the beginning of their career; making mistakes they solved decades ago; and (worst of all) dismissing everything they know as utterly irrelevant.

Think I’m exaggerating? SAN and NAS look suspiciously like DASD, just on faster hardware. Services like Azure and AWS, for all their glitz and automation, aren't as far from rented time on a mainframe as we'd like to imagine. And when my company replaces my laptop with a fancy "appliance" that connects to Citrix VDI session, it reminds me of nothing as much as the VAX terminals I supported back in the day.

My point isn't that I’m a techno-Ecclesiastes shouting "there is nothing new under the sun!" Or some I.T. hipster who was into the cloud before it was cool. My point is that it behooves us to remember that everything we do, and every technology we use, had its origins in something much older than 20 minutes ago.

If we take the time to understand that foundational technology we have the chance to avoid past mis-steps, leverage undocumented efficiencies built into the core of the tools, and build on ideas elegant enough to have withstood the test of time.

Got your own "vintage" story, or long-ago-learned tidbit that is still true today? Share it in the comments!

  • Ah yes, the what was old is new again but with the names changes to provide for new marketing to the unsuspecting.

    Don't knock the old hardware.  I still have an old IBM Thinkpad (200Mhz Pentium) running windows 95.  Why do you ask ?
    Some commercial type radio programming software requires access to a true DOS environment and the radio interface requires the timing you get from a true serial port (RS-232) which you don't get from todays usb-serial port converters.  (Motorola is a good example, good older radios but programming environment is specfic). 

    I also have a somewhat newer compaq (mid 2000's) laptop running win 2000 for a number of Kenwood commercial radios.  Also for the newer software requirements and again a real RS-232 port.

    So Win95 is not y2k compliant, nothing I do with it is date dependent.  It remains air gapped, it is slow and it still works.  Did I say it was slow ?
    Win 2000 also remains air gapped.  I transfer any new software via cd-rom or SD card from a current machine.

    Todays technology is great, but sometimes you need to support older hardware because it provides things todays hardware doesn't have anymore.

    In many ways IBM did it all back in the 70's, 80's, 90's, 2000's as Leon mentioned above. 

    Most everything today is the same concept just renamed for marketing with a bunch of new hype to make it seem all new....again. 

    DASD farms = SAN, NAS,etc.

    VM = they did VM back in the 90's maybe even earlier than that.

    Rented computing time, that goes back to the original mainframes.

    Hosted services...see above item

    and the list goes on...

  • Wanted one of these so bad I could taste it, but couldn't afford it.  Spent hours standing at a counter at the local geek store in the 80's renting time on one though.  It was like $2/hour or something, and I couldn't get enough.

  • Ah, the old draggable Compaq.  I later had a dedicated Sniffer on a Dolch.  That was a pretty serious machine, and I saved the company a ton of money troubleshooting all kinds of problems on our midrange, token-ring and early ethernet networks.

  • Plug and Pray emoticons_grin.png I remember those days. And also trying to find jumpers to use. Pesky little things always disappeared. Especially in schools. Which reminds me ot the students stealing the mouse balls.

  • I use these same colours still for my telnet application emoticons_grin.png

    Nothing like good old monochrome.

THWACK - Symbolize TM, R, and C