Skip to main content

Computer languages I learnt before university

I was thinking about the various languages I have learned over the years and why. Here they are in rough order. I don't think there's a great insight here, just a personal reflection.



Around age 6, I was sent to the Cavendish Laboratory at Cambridge University to a sort of camp for bright kids. I asked a man (undoubtedly a professor or lecturer from Cambridge) to tell me how a computer worked. This was the early 1970s and I'd only seen computers on television.

The man sat down with a piece of paper and drew a long strip of boxes and described a machine that looks at the boxes and decides what to do next. He also showed me a language for programming this strip-of-boxes-machine.

He had described both a Turing machine and also a register machine and I was absolutely fascinated: computers were so simple!



My first hands-on time with a computer came via a teletype that no one seemed to touch. It was kept in the corner of a room at school and connected to some far away machine. But it was possible to program it in FORTRAN. I don't recall ever being told what machine I was typing to, only that it was possible to prepare simple programs in FORTRAN. I mostly wrote some simple mathematical programs (such as calculating the value of pi or factorials). Magic! (when it worked).

Pretty sure is was an ASR 33 Teletype like this:

By Bubba73 (Jud McCranie) - Own work, CC BY-SA 3.0


The school entered the 'home computer' era with a Sharp MZ80K which I spent hours in front of first learning its BASIC so that I could write simple programs (including something called STATPAC which was a package for doing statistics: think, really, really simple R).

That machine still works and runs my old programs. The school was kind enough to let me take this computer home during the holidays. This was the first machine I knew inside out.


But to get any power from the machine it was necessary to learn Z80 assembly language (and the machine code since I didn't have an assembler to everything was typed in as opcodes hidden inside REM statements in BASIC programs). This didn't seem hard at all, more like a crazy game where the moves are limited and you have to work with them. I obtained a copy of Rodnay Zacks' Programming the Z80 at great cost and devoured it.


At some point the school got a network of Research Machines 480Z machines and on these we were able to program in BASIC and machine code. We later got an assembler and I wrote some quite large assembly language programs, such as one for scooping up network packets and analyzing them, another for spying on disk access and a complete 'network management' system.

But PASCAL was a bit of a revelation because suddenly programs that had been structured with subroutines (GOSUB or CALL) and rough and ready data structures were no structured with actual functions that operated on well-defined data. And there was a compiler.


I had a BBC Micro Model B (in fact I still do) and it, of course, I programmed in BASIC and 6502 assembly language, but FORTH suddenly became popular and I figured I had to try it out since this whole 'stack-based programming' thing seemed interesting. And FORTH on the BBC Micro was fast. It came on a ROM that was plugged into an expansion port.

I wrote a lot of fun programs in FORTH but it ended up feeling like an academic exercise. Fun but never going to really catch on. Of course, that's before I got to university and wrote things using Common LISP, ML and Occam :-)


Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of