I thought the course conveyed those takeaways well, though some more than others. For example, I didn’t end up collaborating a whole lot directly since I worked by myself on all the coding projects. However, my understanding of iterators, containers, constructors, and efficient object oriented design have all been positively shaped by the course material and the assignments.

I started becoming a lot more comfortable programming in C++ which was my goal coming into the class.

It forced me to pay attention to class much more than I have in any of my other online courses. It wasn’t high pressure and as much as the idea of getting cold called sounds annoying, there weren’t any stakes so I didn’t mind it.

I didn’t attend any of the office hours but it seems that the TAs offered very frequent office hours for anyone who would need it.

Similarly to the office hours, I did not attend so I don’t have any useful feedback for them. Its nice to know they were available at the very least.

I’ve never used GTEST before this class and I’ve gained at least a slightly more advanced knowledge of how makefiles work. Same goes for astyle, doxygen, cppcheck, etc.

Writing code that is infinitely extendible is the ultimate goal and careful structuring of object relationships can make it very clean and prevent coupled dependencies.

It had never occurred to me that using getters/setters arbitrarily to expose class members was bad object oriented design since its what we learned in 314.

This is maybe beyond the possible scope of the class, but I feel like we should at least mention some common design patterns. Additionally, I didn’t get much out of the blogs and papers.

--

--

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