September 2, 09 - Two Chapters and an Interview

Filed under: by:

Reading these two chapters has been an eye opening experience. I went through the education program at BYU, did student teaching and worked in the schools for a couple of years without ever really understanding the principles of technology instruction discussed in these chapters. I’ve never felt as though I was a successful teacher and I think I now understand why. At times it seemed I was a really good teacher and at other times I felt very ineffective. I now see that the times when I felt I was doing well were times I was successfully directing the natural energy of the students and the times when I failed I was failing to successfully re-direct that energy. I used the same methods but couldn’t understand why I got different results. The problem, it seems, with my attempts to direct the students’ natural learning was that I was not evaluating why there was a loss in their desire to learn. If I had recognized the differences I could have chosen a more effective way to re-direct their learning energies.

I am also fascinated by with the distinction these chapters drew between technology and science. Most of my life I have thought of myself as a scientist and always thought the realm that truly belongs to technology of being within the sphere of science. I now understand that while one affects the other, they are 2 distinct disciplines working on different problems.

I interviewed my friend Mike who builds computers. The very nature of building computers requires one to design. Lots of different criteria go into designing a computer, such as what will it be used for. Resources that come into play include how much is the client willing to spend and what products are available (RAM, motherboards, CPU’s, etc). With an idea of what the machine has to do and price range in site, Mike said he starts with selecting a motherboard and a case to fit it. At first glance, this seems like a natural place to start as these components are essentially the physical foundation of the computer. However, I asked if it wouldn’t make more sense to pick out the CPU first so as to make sure it will have the power to do what his client wants it to do. With the CPU picked out, you could then select a motherboard to fit it instead of the other way around. Enter around aspect of design: bias. Mike said he picks the motherboard first because he prefers a specific kind of socket (the part of the motherboard which allows the CPU to interface with the board). For better or for worse, bias probably always plays a part in design. And why not (to a point), after all, there are no “right answers” in design. Once the motherboard and processor are chosen, he picks out the RAM which will work with the motherboard, trying to get the fastest he can but keeping in mind what the client needs – to try and save them money if they’re price conscious – or the fastest, best RAM he can (within the overall budget) if the client wants the best machine they can get for a particular price. Using similar criteria, he picks out a graphics card, hard drives, optical drives, and other peripherals. Then it’s time to choose the power supply. This choice is dictated by how much power the machine will need to run all of its components. Finally, Mike says the most important thing to remember when designing a computer is to remember what it will be used for. Resources may affect this, but if you forget the end goal the design will suffer.

0 comments: