generated from mwc/lab_dice
0ffe049e3d
methods. 1. I find this to be extremely helpful in the learning process. It is exploratory thinking and learning, but in reverse. You are given the elements and the answers, then asked to decipher them. Explaining what the steps mean is like teaching the steps to another person. This is one of the ways that I have always learned best. If I teach anotehr person the information then I am not only understanding it, but I am able to break it down into pieces. This would be excellent to use in a CS classroom as well. Giving student the chance to break down an answer into pieces, then explain them to one another would be a fun means of reflection and learning. I did find that the docstrings were easier to write when I wrote the two sets of """" first, then tried to break down the code. It seems silly, but this way I was able to see the colors that the words of the code were in. I realized how much that helped me to distinguish the elements from each other. 2. I think I will use docstrings, but as I reflect, I find that in the past when I have used them that they are informal and a little messy. I am thinking back to te drawing project. My docstrings on that project were a little unhinged to say the least. I think if I continue to include them in the future that I need to work on my organization and intentionality. Overall, I think that would make the entire coding process easier. |
||
|---|---|---|
| .commit_template | ||
| .gitignore | ||
| dice_stats.py | ||
| die.py | ||
| play.py | ||
| poetry.lock | ||
| pyproject.toml | ||
| yahtzee.py | ||
| yahtzee_goals.py | ||