Last year's CSC108 ended with a quite challenging exam, but regardless of which, I'm here once again learning from Dan in CSC148. Although the first few weeks had been a hassle managing courses due to conflicts, I still had the pleasure to learn about object-oriented programming, stacks, and exceptions in Python.
The first week was oriented in object-oriented programming. It was not surprising to see some revision in the first lessons. The fundamental basics of constructing classes were taught last year in CSC108, but it seems that the following semester will be focused on them. Dan introduced a method of designing a new class, of which it uses noun, attributes, and operations to break down the general description of a class. Dan also took time to address how these terms, e.g. "attributes", can have different names. For instance, "attributes" can also be called "instance variables" or "object state". Albeit having a pool of names introduced at the same time is a logical and common way of teaching, it is nevertheless confusing for me. To solve this problem, I revisited my notes after class and categorized the terms. This is a copy of what I have written:
"noun/ class name
attribute/ object state/ instanced variables
operations/ object behavior/ function names"
It seems like a silly and trivial problem, yet it helped me tremendously in organizing and understanding what I've learnt. Afterall, one cannot build a house without a strong base. Other than that, everything seemed quite straightforward. As a side note, I'd suggest reading 15.7 and 15.9 from the textbook as the lecture didn't go over that.
Here's a question to other SLOGers! Did you do the exercises in the recommended readings/references? Also, did you notice people gaming during lecture? To tell you what, I'm not even surprised. Meanwhile, the closet nerd inside of me wanted to join in the Hearthstone games or Minecraft adventure...
No comments:
Post a Comment