What are you most proud of doing last week?
I finished my Systems for ML exam — it’s one of my favorite classes and although the exams are tough, I feel like I’m learning a lot from them. Hopefully it went well!
What ability or skill did you use to make that moment the most proud of?
My ability to study and review content effectively. I’ve spent many years studying for hours on end before an exam trying to learn every topic from scratch again. All this ever did was confuse me and my understanding of topics I’ve already learnt. I now study lectures immediately after class, and then review my understanding before the exam. It’s proved to be more effective than cramming all the content at once.
What impact did what you do have on other people?
This didn’t really impact other people, it’s more of a personal achievement.
What did you think of Paper #10. Why getter and setter methods are evil.
It was an interesting read! There seems to be many use cases for getters and setters and they are not things that we can completely get rid of, but I now understand why I have to be more careful in their use and how they’re not entirely object-oriented.
What did you think of Exercise #7. Vector2.
It was hard, but mostly because of all the tedious information. I think doing Vector the second time around was definitely useful and I’ve actually had time to understand the concepts better.
What did you think of Exercise #8. Vector3.
It was much easier than Vector2, but I struggled for a bit on how to use Allocator.
What did you think of move constructor, and move assignment? (This question will vary, week to week.)
Similar to copy assignment and copy constructor, these seem to be integral parts of building structures, and were very helpful to learn and implement.
What made you happy this week?
I got to go home for the weekend! It was Diwali, so I spent a lot of quality time with my family.
What’s your pick-of-the-week or tip-of-the-week?
My tip of the week: design your code before actually coding. It might even be helpful to map it out on paper. As computer science students, I think that we tend to jump into programming far too soon and waste a lot of time re-designing when we find parts of the code that break. Instead, it saves a lot of time and energy to design thoroughly, and then code quickly.
