1. What did you do this past week?
    I wasn’t very productive in terms of courseworks this week. There weren’t major dues except for Collatz, but that feels like a long time ago. It was a little stressful preparing for the career fair/networking and info sessions, but I handled it. Kind of.
  2. What’s in your way?
    There are a lot of materials from all the courses that I need to review for since the exam weeks are coming. All of the materials from all the courses are new to me, and I am just not sure where to start.
  3. What will you do next week?
    I will review for my exams and try to get E for quizzes. A detailed to-do list and a scheduled task board might be helpful.
  4. If you read it, what did you think of the Paper #4: What Happens to Us?
    I have actually read this article from the previous class with Dr. Downing, and is a good article. A lot of cases in the article reminded me of the WiCS talk that Prof. Norman hosted during CS439, which themed on how the accumulation of seemingly little jokes or attitudes on the daily basis is what makes the most minorities feel that they don’t belong and eventually leave.
  5. What was your experience of Collatz, exceptions, and types? (this question will vary, week to week)
    I did the Collatz project in C++ in my previous class with Prof. Downing, but I think it’s a lot more friendly in Python since we don’t have to deal with the integer overflow. That was a huge pain when I last did it! It made a lot of sense as the mechanism of Python int was introduced today, and indeed I agree that the design is very elegant.
    Exceptions and types are a lot more familiar to me for I (and most other CS students) have used them since the very first semester of freshman year. Python is different in type handling than any other languages that I used in the past, though.
  6. What made you happy this week?
    My roommate baked some really nice cookies.
  7. What’s your pick-of-the-week or tip-of-the-week?
    GitHub does not supports pulling repos via password-login. Instead, personal tokens that are like one-time passwords are used.
    Also VSCode ssh-containter extension allows you to code, use terminals, and accessing/editing file system of a Docker image all in one window! If you are already familiar with EMACS and terminal operations then forget about it, but otherwise I think this is pretty neat and is a lot less stressful than switching around between PuTTY, winSCP, and code editor.