CS 373 Blogs: Week of 30 Aug — 5 Sep

  1. What did you do this past week?
    This past week we introduced and went over project 1: Collatz. We talked about what the Collatz conjecture is and how to calculate it as well as how we can modify our code to make the calculations of cycle length over different ranges more efficient.
  2. What’s in your way?
    I still need to complete the project before it is due on the 13th (Monday of next week) as well as work on my working environment for python since this is the first university class I’ve had to do any work in python for.
  3. What will you do next week?
    Next week I will complete project 1 before it is due on Monday as well as show up to class prepared to learn!
  4. If you read it, what did you think of the Paper #2: Makefile?
    Makefiles are super convenient and thankfully I’ve had experience with them in the past so the file was much more digestible than it would have been. I’m still not completely sure how I would go about making a makefile for my own project from scratch since all makefiles I’ve used in the past have been provided or I simply modified a makefile provided for a previous project in the same working environment. But either way, I’m very comfortable reading the makefile for Collatz.
  5. What was your experience of assertions, unit tests, and coverage? (this question will vary, week to week)
    This week was very standard for a class with professor Downing and since I’ve taken a class with him in the past where he drilled assertions, unit tests, and coverage into us the whole semester I’m very comfortable using them. I suppose the only thing that I’m not too sure on is using them in python since last time we used C++ and used google test and gcov
  6. What made you happy this week?
    I gotta say, having the long weekend is very nice and chill.
  7. What’s your pick-of-the-week or tip-of-the-week?
    My tip-of-the-week as we go into project 1 for this class is to take Downing’s advice and write your unit tests before you begin to write your code. It gives you the benefit of being able to test as you are coding and forces you to have a good idea of what you’re going to write as you begin, wayy reducing clutter.