You might be wondering what you need to be doing to "get into Computer Science". You might be looking at A Level options and trying to decide whether computing is for you. This is a tricky stage in your life. Up until now you've probably worked in a wide range of subjects, and quite enjoyed a few of them. Now you suddenly have to narrow your field of study and focus on what you really want to do for the rest of your life. Scary times.

My advice (writes Rob Miles) would be to try and think about the things that you enjoy doing, and try to get to do them as much as possible. If you like digging holes in the ground and seeing what's there, then archeology might be worth a whizz. If you like solving problems and trying to make things work, then perhaps you might enjoy something computer based.

From the point of view of studying Computer Science at university, it is fair to say that a good science/maths background is important - particularly if you want to get into games programming. However, if you enjoy doing things like english, history or geography I'd strongly advise you to keep those up in some way if you can, perhaps by taking such a subject up to AS level. There is more to being a computer scientist than just writing code, you also need to be able to communicate and express yourself, and something like history, where you can discuss and debate subjects from different viewpoints, is very useful.

Also, if you do things like athletics, public speaking, amateur dramatics, school newspaper, DJ work etc these are very useful as they "round you out" as a person and make you much more interesting, so remember to get out there and do stuff. And make sure that what you do ends up on your CV. You should be proud of the things you do and prepared to talk about them. A blog is a good idea too, it is a good way to practice writing and potential employers love reading things like this. However, be very careful when you write such a thing, remember that everyone could (and might) read it.

From the point of view of finding out what people in computing actually do, I can recommend a few books to read. Some are a bit technical, but I think they are worth the effort:

Why Software Sucks: a very amusing description of what drives software engineers, and why we are not as good at providing solutions as we should be.

Soul of a New Machine : very good description of what engineers do and why they do it. A bit long in the tooth now, but I still enjoy reading it.

MicroSerfs : a geeky soap opera.

Code Complete: a big, scary book about the craft of programming. Best read once you have learned to program a bit.