CS371P Spring 2021: Uma Sethuraman

Blog Post 12 — CS371P: Object-Oriented Programming

What did you do this past week?

I worked on the Darwin project with my partner and submitted that. We finished most of the Darwin project last week, so we only had a few tasks left to do this week. I had a project for one of my other CS classes (iOS Mobile Computing) due this week as well, so I finished that with my group. I also worked on assignments for my other classes.

What’s in your way?

Nothing major is in my way. I have more exams and project deadlines coming up since there are only a few more weeks before the semester ends.

What will you do next week?

I plan to get started on project 5 for this class. I will also continue working on my project for my other CS class. I have assignments and quizzes in my other classes so I will prepare for those as well. My course registration for next semester is also next week.

If you read it, what did you think of the More getters and setters?

It was an interesting read! After designing the classes for the Darwin project, I feel that I have a better understanding of how to avoid getters and setters.

What was your experience of sequence containers, container adapters, and associative containers?

The lectures on sequence containers, container adapters, and associative containers were very interesting and useful. I am familiar with some of these topics through my past courses such as Software Engineering (also taught by Professor Downing). I also learned some new concepts in these lectures too, so I plan on reviewing those new concepts again on my own this week to make sure I have a solid understanding of them.

What made you happy this week?

This week was quite hectic for me because the Darwin project and my iOS Mobile Computing class project were both due this week. Finally submitting both of these projects made me happy!

What’s your pick-of-the-week or tip-of-the-week?

My tip-of-the-week is to remember to comment your code as you are writing it. It’s easy to get caught up in just getting the code to work and then push off the commenting to later. But I’ve found that commenting your code as you go is usually more efficient and makes the code more readable. This approach also helps you have a better understanding of why you implemented something a certain way, which can be useful when trying to find the origin of a bug.