function.
I think these are an amazing feature in the coding process. It gives
me a tuch stone so I know exactly what I am looking at and how it works.
In the drawing project, I think these will be key to creating in bite sized pieces
and troubleshooting.
function in each iteration to fit the prompt. The first two were similar with
different starting points. Then the final example had a change to the stride as well.
Ranges made a lot of sense to me. I think it might have to do with the
concrete nature of the function. I really liked the use of the stride
factor. It seems like something that would be helpful in a lot of differnt cases, but with minimal
changes to the function. In short I like the versitility.
One thing I am unsure about with ranges is if they are applicable in instances such as the dawing lab.
If they are countihng numbers, can they be used to create physical representations of things? Or
are they more usable in numerical senses?
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.
Rebecca Hankey
rhankey