I remember the Commodore 64. Too cool for school and WAY ahead of its time because no one had ever heard of computers in the home. The classes I took in computer programming when I was in eighth grade and high school included BASIC, COBAL, and FORTRAN. Today the modern programming languages have awesome names like Java and Python. New software today is a common marketplace entrepreneur’s invention, not a highly scientific endeavor brought about by a team of lab techs. Backdoors used to be sacrosanct to programmers fixing issues and now they are convenient utility features built in for people who have forgotten their passwords. Computer games used to be words on the screen that a user made choices about, not interactive video reality simulations. If we wanted video interaction we went to a video arcade or played on the (also new) Atari home system where a joystick was the only real interface.
In today’s world where computers are more common than television sets and new apps can be downloaded for a few dollars, we have distanced ourselves from the beginnings of the Mobility Age that started thirty years ago. The dangers of computing progress include forgetting the preceding knowledge base of original programming practices.
Designer viruses and spyware have risen in droves over the last ten years, as have the software packages to protect home computers and “clean up” programming that can debug and fix many common program networking issues. While the IT world has rapidly advanced, the “Old school” contingent of programmers still remains. Large companies and software start-ups have invested quite a bit in designing their own systems and, at times, system languages. It matters a bit more these days which environments an IT person has worked in, (aka. “Whose programming are you familiar with?”), than that an IT person knows a certain set of computer languages common across units. The scary part of this scenario is that while “Old school” computer languages may be almost dead, the “New School” IT people may not be aware of the damage that old programming languages and scripting could incur on systems too far removed from where computing started to become part of everyday life. History cannot afford to repeat itself, but history cannot be forgotten or we endanger our progress.
My generation spans the gap. We remember where today came from and we live in the present with an eye toward the future. In fifty more years, there may not be anything left of “Old school” programming knowledge other than moldy records kept in academic archives. I find it is sad to think that only thirty years have passed, and BASIC, COBALT, and FORTRAN are already ancient historical artifacts. “Old school” is still around and “New school” is the cool school, but our future keeps moving forward. In the world of IT and computing the dinosaurs are fossilizing and the planet may have lost precious information that could create a deficiency in knowledge regrettable to maintaining our evolutions.