generated from mwc/lab_iteration
Now it reads using the for_in command and only needs to be prompted to move forward and turn once. I am finding that the directions you have written are clear and very easy to follow. Then when it comes time to work through a checkpoint, I am struggling to apply the informaiton that was given to a task. It is like I know what it means when I read it, but then I get lost and cannot figure out how this information is applicable. For this check point I worked ahead a little and saw that there was a range command. I thought it must be applicable, but was not sure how. I talked through it with a couple people and then looked up similar simplification examples to see how range was used. Then there was some trial and error to get the details right. |
||
---|---|---|
.commit_template | ||
drawtiles.py | ||
poetry.lock | ||
pyproject.toml | ||
ranges.py | ||
square.py | ||
tile.py | ||
tile_grid.py |