Week 3

This week, we had our first test in CSC148, and it was quite interesting. Most people complained that there wasn't enough time to complete all the problems, but I personally thought that it was enough time to write the docstring down for the situations posed. That's the main point of the class, so that should be the focus of the answers in the test. Hard program code is nice and all, but the class stresses program design, so docstring is much more critical.

Also this week, we've learned about linked nodes, a unique array type used for better memory conservation. While it is slightly impractical in my head, I can use the usefulness of having a very conservative array form. The link nodes could be very handy to work with when trying to insert an object in the middle of an array, but so long as you have the specific values about that array or something identifiable. Else, well, back to the drawing board.

Week 2

This week was all about building off previous programs through understanding them. A hefty statement, but one that I find makes sense if one was a program designer. By utilizing the system of subclasses and superclasses, programs can be much more efficiently designed as long as a docstring is present to explain it all

Additionally, we were taught various new ways to think logically about program specifications. On a specific example of coding line recognition, I have thought up of a solution that would work in a very specific mindset and situation. However, many other solutions were put up that interest me, such as using a broader recognition system so that the program could be much more flexible. No need for insane loops as I thought, interestingly enough.