The term is often stated as having originated from IBM’s Harvard Mark I computer conceived by Howard Aiken. Aiken did earn a doctorate at Harvard University; the computer and its successors were built at Harvard.
The Wikipedia entry notes that “The Mark I had 60 sets of 24 switches for manual data entry and could store 72 numbers, each 23 decimal digits long. It could do 3 additions or subtractions in a second. A multiplication took 6 seconds, a division took 15.3 seconds, and a logarithm or a trigonometric function took over one minute.”
Of course, delving a bit more into history, I ran across “The Myth of the Harvard Architecture” (IEEE Annals of the History of Computing, Volume 44, Issue 3, pp. 59-69) by Richard Pawson. That notes the term “Harvard architecture” was coined decades later, in the context of microcontroller design. It was retrospectively applied to the Harvard machines and subsequently applied to RISC microprocessors with separated caches. It was also applicable to the Harvard Mark III and IV computers.
Another Harvard tidbit is that the Harvard Mark II was the first computer to have a real bug associated with it. The bug was a moth. Also, the term “bug” originated with Thomas Edison.
By the way, Pete Hegseth, U.S. Secretary of War, is a graduate of Harvard University. His concern for “woke ideology” for our military didn’t seem to affect him too much, but that’s history.
Tying Together the Strands
The underlying computer architecture and software implications are more important than what the architecture is called, but often that’s what people remember without delving into the details. One of the challenges with history is that there’s so much of it. “Historians” often focus on a very tiny subset so that they can become experts, which is useful because no one can know it all. And, by definition, what’s known will be a subset of actually experiencing it.
As an example, I’m going to talk about an interest and pet peeve of mine: computer programming languages, their design and use. I use a lot now, and used a bunch in the past, and studied more along the way. I put together the “Do You Recognize These? Programming Language Challenge” based on this long-time endeavor.
Programming history can be useful in the challenge, but my pet peeve is how so many programming language designers ignore or don’t know the history of programming languages. Thus, they repeat the mistakes of the past and miss the solutions that others have developed — history isn’t just recording what happened, but learning from the past.
I’m always surprised when talking with programming language and compiler developers who mostly have a limited view of programming languages, being unfamiliar with competing or complementary solutions. The challenge is that these developers need to consider lots of issues from compiler performance and efficiency of the output to security, ease of use, and so on.
Back to history tidibits: Grace Hopper was one of the first programmers on the Harvard Mark I that used a language called Autocode. Grace Hopper created FLOW-MATIC and was instrumental in the development of COBOL. COBOL got started with a meeting initiated by Mary Hawes, a computer scientist at Burroughs Corporation where I was a co-op engineer many years ago; Grace Hopper was just one of many. I won’t go down the rabbit hole tying Harvard into this, other than highlighting the importance of all the different technologies developed at universities like Harvard.
What’s with the Lead Image?
If you went to Harvard, you probably noticed the image at the top isn’t from Harvard. If you happen to be a graduate of the Georgia Institute of Technology, then you will recognize Tech Tower. Tech happens to be my undergraduate alma mater.
Here’s a history tidbit: I recall some of the ROTC students practicing their rappelling technique down the side of our dorm. It’s just one university out of many that have a relationship with the Defense Department.
Here’s hoping that Harvard’s woes aren’t repeated with the likes of Georgia Tech, MIT, IIT, Cal Tech, and so on. Think about the Butterfly Effect and Murphy’s Law when considering tiny changes such as not sending officers to Harvard.
