- Apr 18, 2001
- 15,708
- 5
- 56
I met with a project manager and the Indian software architect for one of our apps yesterday.
The guy's obviously darn good at what he does, he knows his stuff. He's also a great guy. Always happy to help, smiling, etc.
So me and the PM were talking about old computers during part of the meeting... Osbornes, CP/M, Commodores, BASIC, etc. The architect had no idea what we were talking about! He was completely lost.
We talked some more and figured out why... India didn't have the money for technology during the PC revolutions of the 80's. They didn't see much of anything until Pentiums. And had no desire to waste time learning about obsolete equipment, instead focussing on the future (a great career decision).
So the benefits of ignoring computing history are obvious. But what about the downside? Do you think there's value to having had your hands deep into an 8-bit system? Or is it pointless?
The guy's obviously darn good at what he does, he knows his stuff. He's also a great guy. Always happy to help, smiling, etc.
So me and the PM were talking about old computers during part of the meeting... Osbornes, CP/M, Commodores, BASIC, etc. The architect had no idea what we were talking about! He was completely lost.
We talked some more and figured out why... India didn't have the money for technology during the PC revolutions of the 80's. They didn't see much of anything until Pentiums. And had no desire to waste time learning about obsolete equipment, instead focussing on the future (a great career decision).
So the benefits of ignoring computing history are obvious. But what about the downside? Do you think there's value to having had your hands deep into an 8-bit system? Or is it pointless?
