When writing docstrings, I was trying to decipher what the code was for,
rather than trying to figure out how to solve a problem. It involved some
backward thinking compared to writing code. I found it a bit easier than
writing code (although a lot of the methods referred to each other,
which made it a challenge sometimes).
I think I will include docstrings in the futre with more complex code, so
after writing a block of code, I don't forget what the code was for when
I come back to it later. I think it will be useful in the Games Project.
A class could be used to create an object, such as a molecule in
chemistry. In the class definition, would be functions that could
describe how general molecules behave, look, etc. and then when the
class is called later, certain attributes such as the type of molecule
could be defined. If I am thinking about a class correctly, it could be
used to describe the behavior of a molecule for simulation, but then the
actual individual characteristics of the molecule could be called later.