Week 8 Blog: Kyzer Polzin cs371p

Kyzer Polzin
2 min readMar 11, 2022
  1. What did you do this past week? This past week I didn’t accomplish a whole lot to be honest. I worked a bit on a project for another class and watched a whole lot of The Big Bang Theory.
  2. What’s in your way? My eagerness for spring break. I wasn’t very productive this week because I guess my brain is already going into break mode. It really sucks cause I have a project due tomorrow that I’ll probably have to turn in a little late cause I couldn’t find the energy to focus and get it done in time.
  3. What will you do next week? I plan on working a bit and relaxing a lot. I’m going to my friend’s lakehouse this upcoming weekend for a few days so it’ll be fun to go tubing and drive jet-skis around too. Hopefully I am able to get away from schoolwork for the week too though.
  4. What did you think of Paper #8: Interface Segregation Principle? I wasn’t a huge fan of this paper to be honest. It felt like the author was going on a tangent and his examples were both verbose and unclear to me. I understand the general idea of the paper, but trying to reason through the different listings/code examples only made the principle more convoluted than it really is.
  5. What was your experience of std::array, iterators, and equal? I enjoyed these lectures. I especially found the differences between built-in arrays and the std::array to be interesting. I am still a little iffy on the different types of iterators cause it felt like we rushed through them a bit, but I’ll read up on them a little extra to make sure I have a decent grasp on them.
  6. What made you happy this week? I had an IM racquetball match. We lost, but it was still fun to play some good competition with one of my good friends. We also watched some of our other friends play and they won so that was exciting!
  7. What’s your pick-of-the-week or tip-of-the-week? Mine seems obvious, but after discovering that my roommate didn’t know it existed, I feel inclined to share. Using the autosave feature on VSCode is a lifesaver. It automatically saves your files every time you change something so you don’t ever have to worry about losing your progress. Simply go to File and then click the Autosave option and boom, it’s enabled!

--

--

Kyzer Polzin

Current CS student at UT Austin sharing my journey