Honestly, that is only sort of true.  Some of the emails say, “Lose 30 pounds in 12 minutes!”  And some say, “I am the prince of Nigeria!”  And some say, “I am lonely and looking for a purely physical relationship!”

More honestly, that pretty much comprises the bulk of the email I receive.  Nobody has actually asked how to be more like me, strangely enough.  But that day is surely coming, and since I am a computer scientist, or at least since USU says so, I could start with a list of books that you can read if you want to become a true nerd and rule the world the way I do, which is to say, not.

(So, in fairness, I haven’t actually read all of these or owned them. There are some that I haven’t read, but I read one like it; those are marked in blue. There are some that I haven’t read but think I should; those are marked in gray. There are some that where I read one like it, but I want to read that particular one – they are bluish-gray. And I didn’t list the probably 40-50 CS books I own or have owned and read that are not shown here. So cut me a break.)

Math and English

First off, in order to be a good software engineer and computer scientist, you have to be a good mathematician and a good writer.  Sorry.  You simply can’t be a competent software engineer without a solid mathematical background, and you can’t be an effective one if you can’t figure out how to express your ideas clearly in writing.

Learning to Program

Your next step is to learn basic programming concepts.  In my opinion, you should learn two languages at this point:  Python and C.  Python is a good beginning language, very easy to create real applications, easy to learn, and very versatile and useful in the real world.  C is the fundamental systems programming language.  Knowing Python and C will allow you to program just about anything and gives you a good fundamental background.

Computer Science Fundamentals

Having learned how to write basic computer programs, now is time to get into the science of computer science.

Programming Technique and Methodology

How to write software well.

General Programming

Two other languages you might want to know are C++ and Java.  C++ is much maligned, but widely used, especially for systems applications, games, and other high-performing software applications.  Java is an abomination in every sense of the word.  But it is also very popular and good to know.  If you are going to learn Java, you should also learn JNI, so you can get from Java back to C and get some real work done.

Systems Programming

If you are going to do systems programming, you’ve got to know the specifics of how to program to the environment in question.  It’s worth noting here that the UNIX books basically cover POSIX, which applies not only to UNIX but BSD, Linux, and Mac as well to varying reasonable degrees.  I’ve also included an internals book for the big three platforms (Windows, Linux, and Mac).  And if you are going to program for Mac, you will probably want to learn another language: Objective-C.

UNIX/Linux
Windows
Mac OS X

Other

Every good software engineer should clearly understand open source; hence The Cathedral and the Bazaar. You will find you are missing out on a number of inside jokes if you don’t read The Hitchhiker’s Guide to the Galaxy. And everyone should read The Code Book, simply because it is so interesting.

Image Credits: amazon.com and barnesandnoble.com

• A computer is a unique invention in that, through programming, it can be customized to solve many different kinds of problems.
• Programming a computer simply means to provide a computer with information.
• In order to program a computer we have to translate our ideas into a language it can understand.
• Computer language is just a code comprised of sets of electrical switches turned on and off.

In this post we’ll talk a little bit more about the information given to a computer. Basically, information given to a computer falls into one of two categories:

• Data
• Instructions

Data means a quantifiable description of something. Here are some examples of data:

• G – a single character
• True – a truth value (often called a boolean)
• 5 – a number
• Hello – a word
• AAPL, IBM, MSFT – a list of stocks
• 6’2″, 215 lbs, peppered hair, blue eyes, skinny ankles – a description of myself

We can see that data can be really simple or really complex. No matter how trivial or complex, data is really just a quantifiable representation or description of a thing.

Instructions are simply operations that we perform on data. Here are some examples of operations:

• Add two numbers together.
• Invert a boolean value, i.e. make something that was True into False.
• Reverse a string, i.e. make “Hello” say “olleH”.
• Add another stock to the end of a list of stocks.

No matter how simple or complex an instruction is, remember, it is just an operation being performed on data.

Amazingly, that is all that a computer program really is – performing instructions on sets of data. When we start out, we will use very simple kinds of data and very simple instructions, like adding two numbers together. These simple examples will primarily be using data and instructions that are defined by the programming language itself. Later, we will learn about defining our own instructions and our own data. For now, remember: every piece of information in a computer, and in a computer program, is either a piece of data or an instruction. Don’t complicate it!

• Giving the computer clear instructions so it will do what you want
• Translating those instructions into a language the computer can understand

A computer is very much like a well-trained dog: A computer will always do exactly what it is told, if possible. You may be thinking that this is not correct. Actually it is completely correct. Unless what you want the computer to do is impossible (like divide a number by zero), a computer always does what it is told. Where the confusion comes in is that often a computer is not told to do what we thought we told it to do.

What is sometimes frustrating by a computer is that it does a poor job of understanding intent. It takes every instruction literally; it cannot interpret what you really meant to say. So one of the challenges in computer programming is in learning how to express ourselves clearly so a computer will do exactly what we tell it to do.

That’s only half the battle, give or take. Translating those instructions into computer language is the other half. So what, exactly is the language of a computer?

To understand this, let’s digress a bit and talk about Paul Revere’s midnight ride. Prior to April 18, 1775, Paul Revere and Robert Newman had come upon a code whereby Newman could communicate to Revere the movements of the British troops. They agreed to communicate via lanterns: one lantern if the troops were moving in by land, and two lanterns if the troops were moving in by sea.

Let’s use a zero (0) to indicate a lantern that is turned off and a one (1) to indicate a lantern that is turned on. Here is the complete code that Paul Revere and Robert Newman agreed to:

The first code is the obvious choice – no lanterns means nobody is coming. The second and third codes are just reverses of each other. Since Mr. Revere could not determine positionally one lantern from the other, holding up either lantern by itself in either of Mr. Newman’s hands had to signal the same code – coming by land. And, of course, two lanterns meant they were coming by sea.

If you understand Paul Revere’s code, you can comprehend how computer language can be based on switches. In Paul Revere’s code different combinations of switches, or lanterns, being turned on or off meant different things. Other than having different codes, computer language is essentially the same.

The smallest piece of computer information is called a bit, and it represents the state of one switch – off or on. We use the same notation as we just described – a zero (0) means off and a one (1) means on. The smallest logical grouping of bits is called a byte. On most computers today a byte is eight bits. For example, the byte 01000001 could be used to represent the letter A, 01000010 could represent B, etc.

Most of the computers we used in the late 90′s were called 32-bit machines. This refers to the size of an instruction – 32 bits. Most newer computers today have instructions that are twice as big – 64 bits. For example, on the computer I’m typing on right now, it uses 64 bits – 64 switches – to encode every instruction and every piece of data.

Fortunately for us, we don’t have to actually learn the computer’s language, the zeroes and ones a computer uses to understand data and instructions. We instead learn computer programming languages – like C or Python – and let tools translate our instructions, written in a programming language, into ones and zeroes the computer can understand.

And that pretty much leads us into the last point of this topic. In this series of posts we’re going to learn to program using two different programming languages, C and Python. Each language has a different approach to giving instructions to the computer.

The second language, Python, is what is called an interpreted language. We write code in Python, and then we tell the Python interpreter to interpret our code for the computer to tell the computer what to do. This is kind of like going to the market in a foreign country, with a friend that speaks our language as well as the foreign language. As we walk through the market, we tell our friend to communicate a message to the shop owner, and after having done that, the friend relays back to us the results of our communication.

The first language, C, is called a compiled language. Programs written in C are given to a compiler, which translates the program directly into machine language and makes a runnable application out of it – something the computer itself can run on its own. This is like telling our friend exactly what we want from the market and having the friend compile together all our instructions at home first. Then the friend goes directly to the market and does what we wanted.

Both types of languages, compiled and interpreted, offer two different approaches to the problem of converting our instructions into computer language. Later we’ll cover advantages of each approach. For now, the key is to understand what it means when we say that a program is compiled or interpreted.

So we’ve learned basically four things:

• In order to get a computer to do what we want we have to give clear instructions.
• In order to get a computer to do what we want we have to speak to it in its own language.
• Computer language – instructions and data – is basically comprised of codes represented by groups of switches that are all in certain states of being on or off.
• Computer programming languages are translated into computer language, either via compilers or interpreters.

We’ll start learning to program soon. Stay tuned!

One thing that makes computers hard to understand is that the modern computer is unlike nearly every invention that preceded it in one very key way – rather than having a specific use and purpose, the computer is a highly adaptable invention with a seemingly unlimited number of applications.

Consider, as an alternative, the light bulb. The primary purpose for the light bulb is to convert electricity into light in order to brighten darkened rooms and areas. There have been a number of modifications to the light bulb over time, a number of improvements and variations. Nevertheless, the primary purpose of each has remained the same – converting electricity into light.

Some might say, “Yes, but a light bulb can be used for other things.” That’s true. I can cook with a light bulb to some degree. I can use it as a signaling device or even to make signs or decorations. You can even get more creative: Light bulbs could theoretically be used as a weapon, for example. But we’re really straining now to make my statement wrong. I think we can all agree that, for the most part, the purpose of a light bulb is to convert electricity into light.

Since a light bulb’s purpose is fairly easily defined, light bulbs are easy to understand. Even a small child knows what a light bulb is for.

Now compare that to a computer. What, exactly, is a computer for?

This is a more difficult question to answer. Is a computer a tool for accessing the Internet? Reading e-mail? Managing finances? Writing letters? Playing games? Editing movies? Making telephone calls? Watching television? Listening to music? Driving a car? Cooking microwave popcorn? The fact is, most of us would use a computer to do nearly all of these things and many more, including a myriad of tasks that use computers even though we aren’t aware of it.

This very fact is what is so fascinating about computers, and yet so daunting and intimidating. Computers are a unique invention because they don’t have a single purpose – rather, they can be applied in many ways to do many types of tasks.

The process of manipulating a computer to do a specific task is the art of computer programming, and it’s larger discipline, software engineering. Lots of people think that computer programming is too complex, too advanced, and requiring way too much intellect for normal people. Trust me, I’ve known a lot of software developers in my career. You don’t necessarily have to be that smart to learn to program a computer.

That’s one of the goals I have for this blog – to teach you how to program a computer. Yes, you, a normal person. You don’t have to turn into a nerd to do it. Stay tuned.