Your blog entry must explicitly answer the following questions about the class (mark the questions in bold in your post):
There were no exercises this week for me to complete first, so what is there to brag about?
I turned in project #4, Darwin, on Wednesday.
I posted a cute kitten on Ed and got 17 hearts. (Maybe more by the time you read this!)
I am good at computer.
I helped Ronghua set up VSCode to run the debugger (lldb) on her Game Tech project so she could see why it was crashing. I also gave her a pro tip on how to do project #4 (Darwin) for this class.
I answered some questions about Darwin on Ed. Maybe that helped some people.
I did not like it, Sam-I-Am. Here’s a comment I posted about his
Exporter
and Importer
interfaces:
This is strictly worse than just putting
String
-returning accessors onEmployee
. You’re writing a whole lot of boilerplate that you’ll have to change if you add, remove, or renameEmployee
’s properties. It’s just a bunch of over-engineered object-oriented nonsense.
And another:
All Holub has done here is moved the getters and setters into different places by introducing a huge amount of boilerplate. I see no advantage here over just exposing the same methods on
Employee
.
I was persuaded to go forth and sin no more. I certainly can’t go back and sin less!
In all seriousness, I liked them. They were a nice change of pace from the minutiae of C++.
I was not happy this week, and I don’t want to talk about it.
We had ethics lectures this week that included a lot of talk about the golden rule:
Treat others as you want to be treated.
My tip-of-the-week is the platinum rule:
Treat others as they want to be treated.
See you next week!