You can post a question, answer,

A computer is like a car. They're both complex mechanical devices, and there's a lot going on "under the hood." Yet, most people can drive their cars without really understanding how a transmission works, or what makes an internal combustion engine run. Using Microsoft Word or some other application is a lot like driving a car. You don't need to know much about how the computer works to use them, assuming the person who wrote the application did a good job.

On the other hand, writing a computer program is more like designing parts of the car instead of driving it. Writing some programs is like designing a cup holder - you don't need to know that much about how the engine works. Other programs are more like designing the transmission. You don't have to know the internal workings of the engine, but you have to be able to attach the transmission to the engine, and you have to know what kinds of loads and stresses the engine will put on the transmission.

I'm going to make the following statement (I don't necessarily agree with it, but I think it merits some thought): "our goals as software designers should be to know as little about how the computer works as possible. We should only learn what we need to know to design the particular program we're working on right now." Think about this for a few minutes and then comment on it. You may want to answer one or more of the following questions: Do you think this statement is true or false? Why? If you were using the car analogy above, how could you design the engine so that it would be easier to design other parts of the car later on?