This process was tough. By the end of the last unit, I did think there were concepts that
I was beginning to grasp and implement as habit, but these seemed like learning from the
start all over again. The minimum and maximum definitions made sense and were easy enough to
work through, but when it came to completing the more complex lines of code, I did struggle.
One way I found myself troubleshooting was breaking down the steps of the task even further into chunks
and trying to write a piece of code for each chunk. I do think there might be places in this
submission where I got to the concept, but the way I did so was a little clunky. I tried to find
other way to pair down the "clunky-ness" and some of that seemed successful, while other times
I am not sure if my solutions were actually optimal.
I saw a really interesting post the other day, amid scrolling, that encapsulates this feeling perfectly.
The process is like explaining how to make a PB&J to a person. Except you are explaining it to someone
who is has never seen or used such items before. I tell them to take out two pieces of bread,
all good. Lay them down, all good. now with a knife take peanut butter out of the jar, error.
But why is there an error? That is the next step? What is wrong?
Well, I never told them to take the lid off...
But it would never occur to me to tell them that, everyone should just know that, right?
That is how I feel sometimes when I am coding. I feel like i am telling it, just get some peanut butter,
but I never told it to do one crucial step first. The trouble is, I don't know what that missing piece
is most times. So, it is a lot of trial and error. This can be frustrating. But when it does eventually
work, or when pieces begin to work, it is satisfying.
Rebecca Hankey
rhankey