Checkpoint 3: I think in Units 1 or 2 I wouldn't have had such specific conditions.
So OOP helps me target specific goals or problems that I might encounter.
I think OOP makes more sense to me than other targeted code we wrote in Unit 1 or 2.
I am struggling a little bit to understand creation of "." conditions/actions. Otherwise this
seems to be a super useful tool to know.
Checkpoint 2: I think writing the docstrings GREATLY helped me understand the code.
I would love to get in the habit of utilizing this for any new code that I might
encounter, if time permitting. It helped me analyze the step=by=step process of
the running code. It was different in a sense that I thought it was more intentional
than writing the code. When I write code I start with a very rough draft of it
then fixing it as I go. I think if I start thinking of code in the way I wrote these
docstrings, my understanding and skills of coding would improve.
Checkpoint 1: I am not familiar with classes at all so I am still
a little unsure of what I could implement this on. Maybe for things that need
to run multiple times until it corresponds to a certain value... The first
thing I can think of is hacking! Like in the movies the hackers run bunch of
passwords until they find the right one, lol! Since we're also in the game unit,
I remember there was these dressing up games that would score your outfit for certain
events. I wonder if they utilized a similar thing where they went through various combinations
that the players made and scored if they were matching (like three of a kind, etc.).
