Skip to main content

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 

One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only register was an accumulator.

The simple instruction set would have made for a very easy understanding of how complex programs are able to be built out of simpler sets of operations and data.

Opcode Mnemonic Operation
0INPRead a card into memory
1CLAClear accumulator and add from memory (load)
2ADDAdd from memory to accumulator
3TACTest accumulator and jump if negative
4SFTShift accumulator
5OUTWrite memory location to output card
6STOStore accumulator to memory
7SUBSubtract memory from accumulator
8JMPJump and save PC
9HRSHalt and reset

There is a much longer write up that anyone interested in the beginnings of computers should take a read over. I am hoping to make up my own DIY CARDIAC and try writing some fun programs and if I do I'm going to be sure to post about it.

Comments

Kevin Veroneau said…
Hey, great article and thank for you the inspiration. After reading the article, I took it into my own hands to write my own simulator for the Cardiac in Python. I have past experience with bytecode engines in Python, so this project was more or less for readers of my own blog, as I formulated a nice introduction tutorial to how one can build a basic CPU simulator in Python. I hope you can link to it, Building a CPU simulator in Python, this article will also appear shortly on Planet Python.

Popular posts from this blog

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…