The one piece of information that every software engineer needs to know

by Michael (michael@code4life.com)

Time travel is eventually going to happen. We're eventually going to be trust back in time, maybe 100 or 1000 years. It'll be against our will, no doubt. As a software engineer, I'm a man born for this time. We software engineers don't have any marketable skills prior to the 1950s. We'd be useless to the Roman Empire. A modern day architect or carpenter or plumber would be a god in the Roman Empire and well beyond past Feudalism. Us CS majors...well, we could design an awesome website for the St. Benedictine Monks, but they'd have to wait 1500 years to get it hosted.

The one thing every software engineer needs to know to be competitive in the distant to the not so distant past...I'm thinking it's how to make dynamite. It's not perfect. It was invented in 1866, so there's a small gap until the industrial revolution when you can invest in the stock market (sell before 1929).

Back

What are you talking about? Time travel is reality. I'm traveling through time right now. It's just that the travel rate is one second per second and only forward.

Anyway, even if we could travel backward in time we'd also need a way to travel through space as well. Think about it, if you travel six months in the past, you'll be floating in space with the earth being on the other side of the sun. Oops!

I very much like the premise of "A Connecticut Yankee in King Arthur's Court". I've ofte
~CrashCodes~

... often wondered how much I'd be able to jump-start an ancient society's technology if I magically appeared in their midst (and spoke the language).

>The one thing every software engineer needs to know to be competitive in the distant to the not so distant past.

I don't know about the distant past. You need to back this up with something. I'm curious.

~CrashCodes~

Back