This week I spent most of time distributing my time between studying for an exam in Marketing and finishing Darwin. My partner and I ran into several issues with our implementation, but because our scheudles did not line up very nicely and because I've had three exams during this project we had to turn it in a day late. While the logic of our implementation worked, we were having trouble optimizing it without rewriting the majority of the code.
Nothing is in my way at the moment that is too major. I'm planning on looking for a partner for the last project, but that shouldn't be a problem.
Next week I'm going to start as early as I can on the last project so that I don't have to turn in another project late. I'm trying my best to make an A in the class and I'm on track to do that as long as I do well on the final project and test.
Class was really interesting this week. We learned about the move constructor which essentially steals the value from what is passed in. It's a strange name for what it does, but it definitely has its uses.
Today's pick-of-the-week is a great article on how you should handle a distributed systems interview. This can be one of the most challenging interview formats for programmers because we don't typically focus on this in our classes. Usually we focus on implementing specifics, but I for one can vouch that I need more practice in complex, scalable system design.