When Should Kids Be Exposed To Computers?

In response to Are Computers for Kids? Gnomie Francis writes:

Well, I’m certainly no parent (16 years old — heh, you’re right about under-18s being part of your audience)!

I was four years old when I first got a computer, and it was nearing my birthday. A neighbor over the road wanted to sell his Sega Master System II (ok, it’s a gaming console, not a “computer” per se), and about 10 different games. The ones I remember are Double Dragon, Sonic the Hedgehog, and Alex Kid in Wonder World (which was embedded into the system’s memory; it could be played by simply turning the console on without a cartridge inserted). I really loved that console. I didn’t see it as a “learning tool” back then, but now I see that it has really helped shape me into the kind of person I am today (as funny as that may seem).

Like, you had to think on boss battles in the Sonic game; you had to be really strategic. But most of all, you had to teach yourself to be precise, so you don’t (for example) jump when you go over a hole (that would result in game over if you fell down).

My next experience with computers (and I’m really going back here) I think I was at about 7 years old. I was in a class at my junior school, and I was suddenly pulled out of class (as were a few others, if I remember correctly). I was put in front of a computer running this game where you had to solve puzzles, and one where you could draw pictures. I really got into it, and it was really fun. I didn’t want to go back to class.

My first “direct” exposure to computers was a few years (well, about five years) ago. My parents bought a 2GHz, 256M RAM workstation, but let me and my brothers use it. That was also my first experience with the Internet. I started learning how to use it, how it works, and started learning the practical side to computing (not just gaming), like doing work, etc. A few years later (me being an artistic person and all), I started using software like GIMP to draw images. Not only that, I read tutorials on the Internet and I knew how to use search engines, like the back-then Ask Jeeves. My childish adventures were being put to use for maybe one day knowing how to do something useful.

But I had no idea how software was made at the time. I thought the software was some kind of magic they put into bits of metal, and it magically turned on and did things when you pressed buttons. I decided to ask a few people, and looked on the Internet. I found out that you write code, and that was where I learned. But I still had no idea how they wrote the code and got it to work. I thought the “code” was something that was put inside the machine, rather than something that is on the disk. (I didn’t even know what an HDD was!)

That magical day came in my second year at high school when I was in a computer class, and the teacher tried to teach us how to build Web sites. We didn’t do anything complex, just simple things, and that was it. We only did it for about a week, but I was absolute fascinated by it. I went home and looked it up on the Internet. I started self-teaching myself HTML by reading tutorials and following them. I started experimenting and trying things not covered in the tutorial. Tables were used for layouts; I didn’t know that then. Eventually, I learned that there was more to Web design than HTML, and started tinkering with CSS, JavaScript, etc. Now, I’ve got the skills of an average Web design student that would probably be about halfway through the first year in some college somewhere (and this is self taught, keep in mind).

This background in Web design reminded me of “code” being used to create software for computers. Light bulbs went off; I found out people called it “programming.” After reading about a few programming languages, I looked up ones recommended to newbies.

Right now, I’m trying to teach myself programming. I’m using this site to learn C++, and I’ve already had an intermediate/introductory level of experience with a few others (C, Java, and Pascal). My skills are very basic, even after a year of self-teaching, probably because programming is a lot more complex than Web design. I’m optimistic that, as with Web design, I’ll eventually reach that magical turnpoint where everything just clicks into place — where I start understanding new things, trying new things, and doing more. I’m getting there.

I really think games are not educational tools, so to speak, but more like “openers.” Rather than giving you facts, they give you challenges to try and figure out and beat. They teach you how to be able to think while also having fun and enjoying yourself. They teach you logic and how to cope with things that are difficult. They are the essential bases for getting your mind wrapped around the way of thinking required to be interested and good with computers.

You’re right about the need to teach kids these things at an early age. If I got my first games console when I was 12 years old, I’d be nowhere near where I am today. Kids also have better learning capabilities — the younger they are, the better.

I know for certain that all the games consoles I have now (Sega Master System, Sega Saturn, PlayStation, PlayStation 2, along with all the games I have for the consoles), will someday be given to my kids when I’m older. I’m going to teach them how to play, and then let them play. I’ll even play with them!