The origins of Space Invaders

When I was at school they had a building which was mainly for the use of those doing their O Levels (the old name for what is now GCSE examinations). There were only two reasons I would get to go to the building: one was for music lessons as for some reason the music department was located there. The second was to attend the weekly youth night they held for each year group.

In the building was a Space Invaders machine and we would split the small amount of money we brought with us each week between buying penny chew sweets at the tuck shop and playing the game. I wasn’t particularly good at it but I do remember one person seemed to have mastered it and stayed on for ages. They also later got a table style PacMan machine.

This week I came across an article in Wired about the 45th anniversary of Space Invaders and the story behind how it was developed including some of the design decisions made. I hadn’t fully realised how much impact it had on subsequent computer games.

It took me back to my school days.

Links

The Space Invaders Creator Reveals the Game’s Origin Story | WIRED/

Related Posts

The ultimate in debugging

Engineers are currently debugging why the Voyager 1 spacecraft, which is 15 billions miles away, turned off its main radio and switched to a backup radio that hasn’t been used in over forty years!


Read More

The battle of real versus artificial deadlines

This excellent article looks at the different types of deadlines and the impact they have. The key point for me, and not something I had seen previously defined, is the distinction between real and artificial deadlines:


Read More

Using AI to find code problems

Ubissoft have introduced a tool that “uses AI” to identify potential coding issues when the developer commits code. They claim it can detect a significant number of errors and even suggest solutions in some cases. There will always be some errors that it will not be able to identify, for example where the implementation doesn’t match the requirements, however this approach could have a significant impact on the amount of time spent debugging. And it should improve over time as it learns more potential errors.


Read More