This is the last CSC148 post I will write. This semester went by much quicker than I expected and a lot happened that I assume not a lot of people were ready for. I found the first couple weeks of this course quite challenging which put a damper on my enthusiasm for computer science in general.
I found the implementation of classes challenging specially since I had trouble understanding and communicating with my lab TA. Thankfully, for the week we went over recursion, our TA changed to a much more capable teacher. Unfortunately this only lasted one week because of the strike. The strike affected me more than I thought it would. It disabled me from understanding the material concisely. In my opinion, this really affected my test mark for term test 2; specially since linked lists were a big part of the test and that was a week we completely missed in lab.
Assignment 3 is when I finally saw the light at the end of the tunnel. I am very grateful that it did not get canceled because it obligated me to truly understand the ins and outs of recursion. Finishing it gave me a lot of confidence and put me back on track for this course.
I actually believe that I can make it in computer science. Hopefully I can prove that, when, I write the final exam (crossing my fingers).
Sunday, 5 April 2015
Revisiting My Past Slogs
I decided to revisit my very first post: 'Why Geeks Should Write'. I believed that writing and keeping a log of what we learned in class is important for computer scientists, however, I was a bit more skeptical about the importance of blogs then I am now.
In my post, I talked about the importance of being able to communicate your ideas, leaving comments when writing code and keeping notes to track your thoughts. I still believe those things are important, although, I would have to add something. When I wrote this post I did not know a TA strike would take place and would have never expected it to affect my courses as much as it did and so would not have been able to predict the following. Slogs really helped me keep track of the material we learned in class when labs had to be cancelled. Reading others' opinions on class components, the work they were doing, and having to write about ADTs and recursion myself, forced me to revisit these topics when weekly quizzes, what usually kept me on track, were called off.
All in all, I found writing slogs much more difficult then I expected. The ability to communicate and keep track of my thoughts is one I am lacking. It is indeed an important skill to possess and hopefully I can convince myself to continue writing logs of my work. I realize that this will help me in the future.
In my post, I talked about the importance of being able to communicate your ideas, leaving comments when writing code and keeping notes to track your thoughts. I still believe those things are important, although, I would have to add something. When I wrote this post I did not know a TA strike would take place and would have never expected it to affect my courses as much as it did and so would not have been able to predict the following. Slogs really helped me keep track of the material we learned in class when labs had to be cancelled. Reading others' opinions on class components, the work they were doing, and having to write about ADTs and recursion myself, forced me to revisit these topics when weekly quizzes, what usually kept me on track, were called off.
All in all, I found writing slogs much more difficult then I expected. The ability to communicate and keep track of my thoughts is one I am lacking. It is indeed an important skill to possess and hopefully I can convince myself to continue writing logs of my work. I realize that this will help me in the future.
Subscribe to:
Posts (Atom)