CS371p Fall 2020: Jesse Huang

Jesse Huang
2 min readNov 9, 2020

Blog # 11

What did you do this past week?

I finished Darwin on my own in a rush the night before it was announced there was an extension and found myself very slowly writing the unit and acceptance tests the next day. After Thursday when most all of the projects were done I binged tv and games for the first time in a while, but it’s time to get back in!

What’s in your way?

I have a new computer vision project that I’m also worried about again as the concepts are usually hard for me to understand and I have to replay lectures a couple of times to understand. Hopefully, I’ll distribute my time better this time so I won’t feel rushed.

What will you do next week?

I’m planning to apply a little bit for more interviews hopefully before I accept an offer, but I’ll probably mainly just focus on projects again and catching up on lectures. On the weekend I hope to make Ratatouille which the French have a bone to pick with because to them it is Tien or something I dunno.

If you read it, what did you think of The Dependency Inversion Principle?

This definitely made sense in the context of our darwin project in how to avoid those huge switch-case statements and how abstract classes provide flexibility and scalability.

What was your experience of continuing to implement std::vector, move semantics, and allocators again? (this question will vary, week to week)

In all, there is a bunch to remember and to review later for exams. It makes sense that the vector class has so many constructors and options to take in different parameters in order to to be able to store any class type. I think allocators were probably the most simple to understand because we did a project over it recently.

What made you happy this week?

A very very nice lull in the project cycle. I also made omurice like the one popular guy in Japan on Youtube where he cuts the pocket of egg and it splits over the rice.

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

I’ve recently read about slow programming which is the idea of taking time to learn the foundations and ins and outs of a language to create more dynamic solutions in contrast to copying tutorials and frameworks and filling in the blanks with whatever produces the outcome you want. It’s pretty much what we learn during lecture, and it should help as a sort of invest now for more later kind of idea.