1. What did you do this past week?
    This past week I submitted project 1: Collatz, and in class we talked about exceptions and types in python.
  2. What’s in your way?
    Project 2 starts tomorrow (in the groups we will do all of our remaining projects in), but other than that I don’t have any current assignments that are out now and due later, so I’ll just show up prepared for class.
  3. What will you do next week?
    Next week we will get project 2 and start it with our groups as well as continue talking about types in Python.
  4. If…

  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.

  1. Where did you grow up?
    I grew up in Austin, Texas and have lived here since.
  2. What was your favorite extracurricular activity in high school?
    I really enjoyed coding in high school and did some UIL CS.
  3. Why did you come to UT?
    I came to UT for the computer science program and to stay local (save money with the option to live at home).
  4. Why are you majoring in CS?
    I’ve loved computers for a long time and have been interested in coding since middle school so it was an easy pick for me.
  5. Why are you in this…

From Professor Downing:

“I hope that the following are long-term takeaways from this class:
-test first, test during, test after; test, test, test
-when designing algorithms, demand the weakest iterators (e.g. bidirectional vs. random access)
-when designing containers, provide the strongest iterators (e.g. random access vs bidirectional)
-build adapters on top of containers and iterators
-
do not use new and delete, use allocators instead
-always look for reuse and symmetry in your code
-collaboration is essential to the quality of your code and to your well-being in producing it
-refactor, refactor, refactor
-make your code beautiful”

So:

  • How well do…

  • What did you do this past week?
    This past week we had class on Mon/Wed and went very in depth about the implementation of C++’s vector class. We talked about how vector is written to support not just the generic type held in the container but also any allocator, user-defined or not. A big takeaway was how much code is reused by functions calling one another so that const/non-const versions of the same function don’t have to be rewitten or especially with comparison operators making it so you only really have to write operator == and operator <.
  • What’s in…

  • What did you do this past week?
    This past week I finished Project 3: Integer by implementing the Karatsuba algorithm for multiplication, and in class we went more in-depth talking about different data structures in C and how their iterators are implemented and related. We had no class on Friday so that’s just about it other than exercise #7: reverse where we implemented a function to reverse a segment of a data structure using iterators.
  • What’s in your way?
    Project 4: Deque has been release so I need to get started on that. …

  • What did you do this past week?
    This past week we started project 3: Integer and started learning more about generics/templates. We talked about templated functions and structs, lambdas, and also started talking about containers in the C++ standard library and what types of iterators they use/how the different strengths of iterators are related.
  • What’s in your way?
    I still need to finish project 3 before it’s due on Tuesday (7/6).
  • What will you do next week?
    Next week I’ll finish project 3 and we’ll discuss more about containers and iterators in class.
  • If you read it, what did you…

  • What did you do this past week?
    This past week we talked about returning from methods/functions (which includes exceptions), the different ways of using const in C++ (variables/pointers/fuctions), iterators, and we began talking about generics/templates. Outside of class, I worked on Project 2: Netflix which was mainly different from other projects in two ways. The first was using boost serialization which mainly was a problem with trying to get it to work with other tools and different versions and whatnot. The second was trying to get the RMSE down below 1.0. I was able to get it down to 1.01 but…

  • What did you do this past week?
    This past week I finished and submitted project 1 (Collatz). In class this week we discussed references and pointers, project 2 (Netflix), exceptions, root mean square error (RMSE), and using Boost Serialization to cache data for project 2.
  • What’s in your way?
    I need to work on project 2, specifically implement the bare-bones solution then gradually make it more complex to lower the RMSE to below 1. Other than that it’s a standard week with quizzes every day and another paper and blog next Sunday.
  • What will you do next week?
    Next week I…

  • What did you do this past week?
    This past week was the first full week of class. We started project 1: Collatz and talked about how to write tests for our code using google test and simply comparing output to expected output, using gcov, and how to properly use assertions. We talked about how we can optimize our code for solving Collatz including minimizing the range of calculated values, caching (lazy, eager, and meta), and being smart about the code we execute in our loop to prevent unnecessary iterations.
  • What’s in your way?
    Well I suppose the most obvious thing is…

Matthew Jagen

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store