If you're searching for a fountain of youth, the easiest way to get that feeling of continual rebirth is to hang around a few tech product launches. Every new rollout comes with the fresh, unabashed feeling that this has never been done before. Ever.
But it has. Apple has been bringing us "one more thing" for more than 30 years. Even the iconic commercial introducing the Macintosh is nearing 29 years old. Newness has never been so old.
Hype notwithstanding, the computer industry has already been through a number of generations. IBM has roots in tabulating companies that began about 130 years ago. That's three 40-year generations of tabulation and computing work without overlap.
In practice, new generations overlap quite a bit. The Internet is easily more than 30 years old, but it wasn't widely open to nonresearchers until about 20 years ago. During those 20 years, there have been at least three different bubbles, each with a feeling all its own.
These generations each have a distinctive flavor, often defined by a programming language or technology. They burst out with newborn fervor before settling into a comfortable middle age. They may not be on the top of the pop charts after a few years, but they're often still kicking because software never really dies. It's always running in some corner of a stack, somewhere somehow.
These new technologies often group programmers by generation. When programmers enter the job market and learn a language, they often stick with the same syntax for life -- or at least as long as they can before having to make a switch. It's not that it's hard to learn a new language; they're all pretty similar underneath. It's just that you can often make more money with the expertise you have, so the generations live on.
Here is our guide to some of the more dominant tech generations in computer history, as embodied by the programmers who gave them life. The list is far from complete, but if you've been coding for any amount of time, you will probably recognize many of these generational traits in yourself, your coworkers, and the programming community at large.
The '60s-era computers received their instructions from a stack of card with punched holes, a scheme that dates to the earliest programmable looms for weaving cloth. Some enterprise programmers talk about old software as "dusty deck," which is largely a metaphor. There was recently a story about a punch card programmer for looms in England that still use the old technology to make lace.
Language of choice: Fortran
Special skill: Not dropping the deck of punch cards
Sign up for Computerworld eNewsletters.