Honestly, I didn't expect much out of this class to begin with. I took computer applications in high school and still remember a lot of the information learned in that class. The first couple of weeks didn't present much that I hadn't already known. I've created surveys, done mail merges, and have created blogs before. Most of the new information came in new techniques and increased familiarity with each of the programs/applications involved. I found the discussion of privacy and the creation of a personal budget spreadsheet to be helpful and interesting. One of the most helpful things in the first couple weeks was the video about captcha codes and how they are being used to help people learn new languages and get physical books into an online format.
The last half of the class presented the most new information by introducing Scratch and solidifying my basic knowledge of how computers work and basic computer specs.
As I said earlier, I had low expectations of this class. But now, at the end of the journey, I've come to realize how much I have learned from the experience. For such a short class,the knowledge gained is both bountiful and helpful to my daily life.
Sunday, 8 July 2012
Week 4 Reflection
This blog will focus on my experiences with both the "blown to bits" assignment and the computer hardware reading assignments.
The first chapter of the "blown to bits" book gave me further insight into the magnitude of the technological explosion that is currently taking this world by storm. It helped me to appreciate the progress this world has achieved since the dawning of the technological era, but it has also made me wary of the extreme risks involved such rapid advancement. It is scary, but also highly fascinating to imagine the technological future of this world.
When it comes to bits/bytes/computer hardware, I learned most of this material either in my high school computer class, or in my sound/recording class (where we learned about binary, memory, as well as how CD's and DVD's work). There were a couple of things that I gleaned from the readings/animations.
1) I had never really seen much of the inside of a personal compter, and the configuration was never really explained to me.
2) In my sound/recording class, we didn't have time to learn how CD-R's, DVD-R's, and CD/DVD-RW's work. I found that information to be quite interesting.
I'm sure there are more things that I could site as things I learned for the first time through this assignment, but these two are probably the most significant.
The first chapter of the "blown to bits" book gave me further insight into the magnitude of the technological explosion that is currently taking this world by storm. It helped me to appreciate the progress this world has achieved since the dawning of the technological era, but it has also made me wary of the extreme risks involved such rapid advancement. It is scary, but also highly fascinating to imagine the technological future of this world.
When it comes to bits/bytes/computer hardware, I learned most of this material either in my high school computer class, or in my sound/recording class (where we learned about binary, memory, as well as how CD's and DVD's work). There were a couple of things that I gleaned from the readings/animations.
1) I had never really seen much of the inside of a personal compter, and the configuration was never really explained to me.
2) In my sound/recording class, we didn't have time to learn how CD-R's, DVD-R's, and CD/DVD-RW's work. I found that information to be quite interesting.
I'm sure there are more things that I could site as things I learned for the first time through this assignment, but these two are probably the most significant.
Week 3 Reflection
I don't exactly remember which week corresponds to which assignment, so I'll spend the next few reflections talking about Scratch,computer hardware/blown to bits, and the final exam/final reflections respectively.
This blog will focus on my experience with scratch, a program that I hadn't heard anything about until I was introduced to it during this class.
At first glance, I found scratch to be simplistic and frankly boring. It wasn't until I was forced to dig deeper and create projects that were more involved than creating a dance that I realized the potential of this program.
My current opinion of this program is that it is a great educational tool to teach people simple programming language. It is not too hard to understand, but complicated enough to get some real work done. I appreciate the opportunity to work with this program, because not only have I learned a bit about programming, but I got to have some fun as well.
This blog will focus on my experience with scratch, a program that I hadn't heard anything about until I was introduced to it during this class.
At first glance, I found scratch to be simplistic and frankly boring. It wasn't until I was forced to dig deeper and create projects that were more involved than creating a dance that I realized the potential of this program.
My current opinion of this program is that it is a great educational tool to teach people simple programming language. It is not too hard to understand, but complicated enough to get some real work done. I appreciate the opportunity to work with this program, because not only have I learned a bit about programming, but I got to have some fun as well.
Subscribe to:
Posts (Atom)