During the first four weeks for CSC 148 class, I learnt many basic techniques about Python. One thing I learnt was how to use subclass. Using subclass was a new topic for me as I did not learn it during CSC 108 class. I also had some trouble with Lab exercises for the first two weeks. However, my TA explained the concept very well that I understood the concept at once. I would like to thank all the TA and senior lecturers in CSC 148 for their efforts.
For the first two weeks, we learnt about Object-oriented programming. We learnt how to use __init__ and how we can use privacy using underscore in Python.
For instance, I tried writing class Drink for __init__ only.
class Drink:
""" Information about Drink on calories and amount
"""
def __init__(self, calories, amount):
""" (Drink, int, int) -> NoneType
Initialize class Drink
"""
self.calories = calories
self.amount = amount
I also tried making class Coke that has Drink for __init__ only.
class Coke(Drink):
""" Information about Coke on calories, amount and the amount of caffeine it contains
"""
def __init__(self, calories, amount, caffeine):
""" (Drink, int, int, int) -> NoneType
Initialize class Coke
"""
Drink.__init__(self, calories, amount)
self.caffeine = caffeine
This demonstrates how well I understand the use of class and subclass.
I also learnt about stack which I already knew since I previewed this material during the winter break. Not only that, CSC 108 also briefly went over the topic on stack. So I had no problem understanding the stack.
I also finished my first CSC 148 assignment with my partner. The assignment was basically focused on how to implement subclass and how we can make a game without any start-up code provided. For CSC 108 assignments, we used to get some start-up codes provided and we just had to put additional code. However, it was different for CSC 148. The only thing we got was an instruction paper and we had to think of writing codes from the very beginning. Although it was a bit of challenge, I really liked the idea that we code the entire thing for Subtract Square game. I also had fun writing up the codes.
The last thing I learnt was recursion and tracing. Although I had trouble with recursion, my TA really helped me understand the recursion. I am confident that I did well on my Tutorial Quiz #3. I really enjoyed learning recursion and hope to achieve 2/2 on the quiz
Finally, I have my first CSC 148 exam next week. So I will study hard during the weekend. I also think that writing this SLOG post also helped me review the materials for the exam. Let's do this, Julian! You can do it!
Friday, January 30, 2015
Friday, January 23, 2015
Week 3: Why Geeks need to write? Because We need to!
Many people think of computer science as just software programming like Python. However, interestingly, computer science involves discussion among computer scientists. A computer scientists sitting in one place typing bunch of codes is not a great computer scientist. A great scientist is the one who can do coding well and discuss his or her idea with other computer scientists. In order to express his or her idea, it is necessary for him or her to have great communication and cooperation skills. Before coming to U of T, I always thought of computer science as a simple software programming. However, during the first, I took CSC 165 where I learnt mathematical expressions and logistics in computer science. This enabled me to widen my perspective on computer science.
This is my first SLOG for CSC 148, but I've written several SLOG posts for CSC 165. Writing SLOG helped me review the course materials covered. I believe writing SLOG posts even helped me with CSC 165 final exam. So I am confident that I can keep up writing SLOG posts just like what I did for CSC 165.
Computer scientists need to write in order to improve the presentation of their ideas and thoughts. I strongly agree with this and I am happy to write SLOG for CSC 148. During the last term, one of my friends who is major in commerce told me that computer science is all about coding. I disagreed with him suggesting that computer science involves lots of discussion just like a businessman. I look forward to writing various interesting SLOG posts during this term.
This is my first SLOG for CSC 148, but I've written several SLOG posts for CSC 165. Writing SLOG helped me review the course materials covered. I believe writing SLOG posts even helped me with CSC 165 final exam. So I am confident that I can keep up writing SLOG posts just like what I did for CSC 165.
Computer scientists need to write in order to improve the presentation of their ideas and thoughts. I strongly agree with this and I am happy to write SLOG for CSC 148. During the last term, one of my friends who is major in commerce told me that computer science is all about coding. I disagreed with him suggesting that computer science involves lots of discussion just like a businessman. I look forward to writing various interesting SLOG posts during this term.
Subscribe to:
Posts (Atom)