So in the latest week of CSC148 lectures and labs, we've dealt with analyzing recursion as well has making our own sub-classes of Exceptions.
I have had previous experiences in applying recursion in my own programs before enrolling in this class, but combined with new concepts we learned in the previous lectures, recursion seems slightly hazy for me. It might also be due to the fact that I never properly learned recursion, aside from its concept and brute-force recursion to only catch stack-overload errors in my programs. I feel it's necessary to go over the material times to even begin to understand it. It's like I got to do recursion for learning recursion in real life. Mind is almost blown.
Errors/Exceptions were like a straight-jab when I was expecting an upper-cut... I have never done Errors nor Exceptions (custom or pre-made) in any of the past programming languages I have dealt with. The try-except was more familiar as I used the equivalent try-catch in Java, but I used it only simply knowing that when my code in try failed it completed what was in the except block. With our most recent lab (third lab) I was able to understand the try-except concept and its relation with errors and exceptions.
Lucky for me, we will still be dealing with recursion in the upcoming lectures, so I have time to catch up on recursion before it explodes in class.
try:
to leave
except:
you have to stay.
maybe
Until next time,
Raymond
