Vic20 Mischief: How a Teenage Prank Sparked My Interest in Programming

Hey there, fellow tech enthusiasts! Today, I want to take you on a nostalgic journey back to the 1980s when I was just a mischievous teenage boy armed with a Commodore Vic20 and an insatiable curiosity for all things tech. Back in those days, personal computers were still relatively new and exciting, and I couldn't resist the temptation to have a bit of fun with them.

Early experiences with computers like the Commodore Vic20 often sparked curiosity and creativity, leading many people into careers in software development.

Discovering the Vic20

Picture this: It was the '80s, and Commodore Vic20 computers were all the rage. You could find them in electronics stores like Dixons and even at unexpected places like Boots the Chemist. These computers were encased in metal display boxes, making them the perfect playground for a mischievous teen like me.

The Perfect Prank

The setup was simple but effective. I had committed a tiny BASIC program to memory – a program that would wreak havoc in the most harmless way possible. It was just about ten lines long, but it was enough to turn an innocent Vic20 into an instrument of chaos.

Here's how it worked:

1. I'd saunter into one of these stores and nonchalantly approach the Vic20 on display.
2. With the confidence of a tech-savvy teen, I'd quickly type in my carefully memorized program.
3. The program was designed to start a timer for about 60 seconds, and then crank up the volume to full blast.
4. After the countdown, the Vic20 would emit an annoying, high-pitched sound that could wake the dead.
5. The final twist: I programmed it to lock the keyboard. No matter what the frantic store staff pressed, they couldn't silence the alarm.
6. The only way out for them was to find the key, unlock the enclosure, and either remove the power supply or cycle the power to stop the commotion.

As soon as I hit the "RUN" command, I'd make a hasty exit, knowing that the Vic20 would play the siren-like alarm, causing chaos and confusion behind me.

Looking back, it's clear that my friends and I were quite the teenage troublemakers, finding endless entertainment in this tech prank. The alarm wasn't some sophisticated sound system; it was just a tiny speaker playing a simple, high-pitched note. But to our teenage ears, it was the epitome of hilarity.

Where It All Started

Little did I know at the time that these early experiments in programming and mischief would eventually lead me to a career as a software engineer. Those innocent days of Vic20 pranks were just the beginning of my journey into the fascinating world of technology.

In today's world of high-tech gadgets and complex software, it's easy to forget the simplicity and charm of those early computers. But it's important to remember that every tech enthusiast has a starting point, and for me, it was the mischievous adventures with a Commodore Vic20 that ignited my passion for all things tech.

Looking back, it wasn’t really about the prank. It was about understanding how systems worked, how small pieces of code could control behaviour, and how technology could be both powerful and unpredictable.

That curiosity is still the same today—it just shows up in very different ways.

So, there you have it – a trip down memory lane to my teenage days of Vic20 shenanigans. As a software engineer now, I can't help but smile at the thought of how far I've come from those innocent pranks. But hey, we all have our beginnings, and mine just happened to involve a mischievous little computer and a whole lot of curiosity.

We all start somewhere, and those early experiences often shape how we approach technology later on.

I spend a lot of time helping simplify systems and make them behave in predictable, reliable ways.

You can take a look at my TechFix service if that sounds useful.

The Commodore VIC-20: My First Computer

The Commodore VIC-20 wasn’t just my first computer—it was the thing that sparked my interest in computing, programming, and building things.

Looking back, a huge amount of what I still enjoy today probably started with that machine.

In the early 1980s, home computers were just starting to become popular, and the Commodore VIC-20 was one of the first affordable options. When I received a VIC-20 as a Christmas present from my parents, little did I know that it would become a significant influence on my life. That VIC-20 became my gateway to the world of computing and programming, and it eventually led me to pursue a career in software engineering.

Discovering Computing

The VIC-20 was a small, boxy computer that came with a built-in keyboard and 5 KB of RAM. Although its specs were modest, it was a versatile machine that could run a variety of software, from simple games to complex applications. The computer could be connected to a TV set or a dedicated monitor and used a cassette tape drive for loading and saving programs.

Learning to Program

When I first got my VIC-20, I was fascinated by its capabilities. I spent hours tinkering with it, typing in programs from magazines and experimenting with different commands. I learned BASIC programming on that computer, and I was amazed at how much I could do with just a few lines of code. I wrote simple games and educational programs.

What fascinated me most was the idea that you could create something from almost nothing—just a few lines of code could completely change what the computer did.

The Social Side of Early Computing

One of the most memorable aspects of the VIC-20 was its cassette tape drive. I spent countless hours recording games onto cassette tapes, carefully labeling them with their titles and descriptions. I also received tapes from friends and classmates, and we would swap them back and forth, trying out new games and programs. It was a social activity as much as a technical one, and it brought me closer to my peers.

Early home computing felt much more hands-on and communal than modern technology often does. People shared tapes, copied programs from magazines, and helped each other figure things out.

As I got older, I continued to use the skills I learn on the VIC-20. I learned more advanced programming concepts, such as graphics and sound programming, and I created more ambitious projects.

What Stayed With Me

Looking back, the VIC-20 was much more than just a computer.

It introduced me to programming, problem solving, creativity, and the idea that technology was something you could build and shape yourself rather than simply consume.

A surprising amount of the way I still think about systems and technology probably started there.

And to top it all I still have my VIC-20 still in its box. Although it is missing its power supply, video cable and tape deck now.

This connects closely to my post about LEGO Technic and engineering mindset, where I first became fascinated by how systems fit together.

It also links naturally to my reflections on visual thinking and how I mentally model systems and processes.

I later even created my own text adventure game called Redcastle, inspired by the kind of exploration and imagination these early computers encouraged.

Understanding technology often starts with curiosity and experimentation.

I still enjoy breaking systems down, understanding how they work, and simplifying technology where possible.

You can take a look at my TechFix service if that sounds useful.

Why I Keep Coming Back to Arduino Projects

I’ve always enjoyed projects that combine software, electronics, and problem solving.

That’s probably why I keep finding myself buying Arduino kits, even when I already have unfinished projects sitting in drawers.

But when "The Most Complete Arduino Starter Kit" appears on Amazon prime at more than 50% off, Hey it would be rude not to. I looked at all the accessories and found myself clicking the buy with one click button and less than 24 hrs later it arrived.

Tech Christmas Day... The box was full of all sorts of colored bits.

This is the 3rd Arduino I've bought over a number of years. The first was a simple learn-to program an Arduino kit and came with some basic electronic components.

Why Arduino Interested Me

An Arduino is a solid-state microcomputer with onboard input and output pins exposed. It's basically a circuit board with a controller about the size of a playing card. It's blue, not that it matters. It's like a mini PLC or Programmable Logic Controller. It can sense the outside world with connected sensors and be programmed to do something that can affect that world. 

What fascinated me was the connection between software and the physical world. Code could suddenly control motors, lights, sensors, and real objects rather than just things on a screen.

So you could connect a light sensor and measure when it gets dark. When it does it can switch on a light. It can be so much cleverer than that though. It can measure how dark it is and can be programmed to adjust how bright the light is.

That was about as far as my projects got with the first one. Although I did make a bubble machine for the boys. It used a servo to dip a bubble eye in a bowl of fairy liquid, raise it up rotate it and a fan would turn on and blow bubbles. It would then lower back into the liquid and repeat. It wrecked the servo eventually as the fairy liquid dripped into its gears of the servo. It was fun when it lasted and the boys enjoyed it.

Projects That Never Quite Finished

The second one I bought a few years later was an Arduino Yun (posh model with Wifi) it was bought with a plan to solve my leaving the garage door opener problem. I can't see the door from the house so would forget and go to bed and wake in the morning to the realization that the door had been open all night.

The door is electric so the plan is to add a couple of limit switches and feed them to the Arduino. It would be programmed to tell me past a certain time that the door was still open. It would tell me via wifi and I would be able to press a button and it would close. This project will still happen someday. I've probably had the Yun for 3 years now.

And on to the third Arduino. It's an R3. I have no idea what's this means. I guess it's probably revision 3 but I still have to read the manual. Out of the box, it looked the same, it plugged into my Mac with a USB cable that provided power and the ability to download programs. I skimmed through the 3 pages of windows installation to get to the Mac installation. Which was 1. download the zip. File 2. extract and run the programming package.

So what came in the box besides the Arduino? Lots of things.

Learning Through Experimentation

The manual comes with 100 or so tutorials on things to make.

Building Things Together

Why did I buy another Arduino? Here comes the excuse... I would like Jamie (age 9) to get involved and what better way to get some son Dad time with Tech than to build things together.

We have done the first couple of projects and so far so good. Jamie has learned a resistor can change the brightness of an LED... The bigger the resistor the less bright the LED gets.

There’s something satisfying about learning these concepts physically rather than just reading about them. Changing a resistor and immediately seeing the LED dim makes electronics feel real very quickly.

I'm looking forward to getting into the more complicated projects and hopefully, as I/we will learn more about the Arduino programming language Also hopefully the Yun will be pulled from my desk drawer and be put into action for its original purpose of telling me when I have left the garage door open. Who knows I might get Jamie to build this project.

Looking back, Arduino projects were never really about finishing perfect products.

They were about experimenting, learning, solving small problems, and understanding how software and hardware interact with the real world.

That curiosity has never really gone away.

This also connects closely to my reflections on LEGO Technic and engineering mindset, where my fascination with mechanisms and systems probably began.

It links naturally to my thoughts on early computing and programming and how experimentation shaped the way I learned technology.

A lot of the same mindset also appears in my post about fixing things instead of replacing them.

I’ve always enjoyed experimenting with technology, understanding how systems work, and solving practical problems.

A lot of that same thinking now goes into helping simplify technical issues and improve digital systems.

You can take a look at my TechFix service if that sounds useful.