Reflection 5

Wheelhouse and Missile Room:
  • What concept(s) that were you unclear about by the end of yesterday but that you now understand better? Describe what happened that brought it into focus.

  • How did your understanding of sorting grow from watching the video to presenting it to the group?

Engine Room:
  • How did spending the time writing out a plan for your book generator change the way you wrote the program itself?
  • How did specifically working with a partner change your coding process?

42 comments:

  1. i was a little unclear about loops but i understand them a little more.
    2. uh.....

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete
  3. I don't think the dancing thing was necessary and I didn't come here for that.

    ReplyDelete
  4. I had no clue how to bounce my sketch back and forth, as well as creating multiple for loops for the same thing. Well, I kinda knew how to already with xspeed and yspeed and the for loop parameters, but now I am definitely more confident in coding with it. By the end of yesterday, I was very disappointed that I didn't understand a lot of this stuff, but now, my frown has turned upside-down!

    We watched the video and applied our knowledge from ourselves and the video, and we just did it. It was weird but somewhat entertaining, I wouldn't mind doing it again even though it was pure torture to forget how to count to ten. I love torturing myself mentally~!

    ReplyDelete
  5. at the end of yesterday i did not understand how to make the two for loops in the army work but today i was able to do it without struggle. By seeing Sam's example i was able to do it on my own. No, i still have no idea what sorting is used for and the point of the activity.

    ReplyDelete
  6. 1. I wasn’t here yesterday so probably how to do loops properly.
    2. My understanding of sorting grew because now I know how to not sort certain things. Also presenting it to the group was odd but a good visual as well.

    ReplyDelete
  7. The best part of today for me was when I didn't understand the for loop but after the ta's explained to me the way it works it was more easy that what I could imagine.

    Also that the video helped me to understand better the way that the if statement and for loop works.

    ReplyDelete
  8. 1)nothing was unclear. I understood everything
    2) I already knew about sorting

    ReplyDelete
  9. 1. I understand the concept of if statements better today than yesterday because I made many if statements and nested if statements. Also, I better understand how the computer runs for loops because of the activity at the beginning of class. Lastly, I feel more comfortable with planning out code because of the flow charts I made on paper before I actually started coding on the computer.\
    2. I was able to pick up bubble sorting fairly quickly from watching the video, and being able to dance it just reaffirmed my knowledge. However, watching the other group do the selection sorting dance did not help me understand selection sorting at all, which causes me to suspect that the video is more informative and the presenting is more fun.

    ReplyDelete
    Replies
    1. To be fair, almost no one knew what they were doing in that group, so that may be why it was so confusing.

      Delete
  10. To be honest, there wasn't really anything I was unclear about, since I have a few years of experience with programming. However, I must say that the activities over the past week really helped me improve my coding skills, as I was able to see the tasks in a bunch of different ways.

    I knew on some level that there were ways in which computers sorted lists, but I didn't realize that there were many ways of sorting. Somehow I had always assumed that all computers had a specific sorting algorithm, but now I know three different ways to sort. (Also, apparently computer programmers would not make good choreographers.)

    ReplyDelete
  11. 1. i did not know how to make rows of ships. it helped to get help from the TAs.
    2. i understood that i never want to to it again.

    ReplyDelete
  12. I now better understand how to use and write the for loop. It helped that we did the exercise today in class. Because we traced the loop to see what would get printed, it helped show the mechanics as to how the for loop works.
    My understanding of sorting remained the same from when I watched the video and presented it to the group. But, being able to physically show how sorting is done was fun. :D

    ReplyDelete
  13. 1 . I understand the need for neatness better, because today I needed to sift through 30 lines of if statements to find a syntax error.

    2. Watching the video, I only understood how to do the sorting, I realized I understood wrong and had to try again (ok, that was while practicing)

    ReplyDelete
  14. Yesterday I didn't really understand for loops but today I sort of kinda get it. Sam going over it made me understand it better. Doing sorting with a group helped me visualize it better.

    ReplyDelete
  15. 1. The concept of using a counter was unclear yesterday, but I understand it better due to the explanations provided by the TAs.
    2. I think the transition from watching it to actually presenting it helped familiarize the concept of sorting with us more than just watching it once.

    ReplyDelete
  16. I was unsure of how you would bounce the robotArmy at the end of the screen and how would you slide the robotArmy at the end. Felipe one of the TAs was able to help me understand how to do this.
    The dancing was sort of confusing but the video helped me understand sorting.

    ReplyDelete
  17. At the end of yesterday I was pretty confused about loops. Now that I have worked with the TA's and the other people in my room, I have a better understanding of how they work.

    ReplyDelete
  18. 1. I understand loops a little better and the difference between global and local variables is explicit. I realized there b mad variables to code/program though. TA's helped, but repetition was the best way to improve.
    2. It didn't. Presentations were whack, so I didn't really learn. The videos were better since they weren't live demonstrations.

    ReplyDelete
  19. no one of the concept because i already knew about the loops and the boolean so for me was not that much hard.

    ReplyDelete
  20. 1. It gave me an outlook on the entire project.
    2. It was more efficient.

    ReplyDelete
  21. 1) It's like having an outline when writing an essay. Really useful.
    2) Two minds was easier, since roles could be divided between the partners.

    ReplyDelete
  22. 1. Spending time planning out the code lead to me and my partner discovering possible code breaking even before we started writing code.
    2. Working with a partner helped with the planning and also brought a different perspective to the planning process.

    ReplyDelete
  23. i understand how to make figures move now. i now know that x along with dx must change in order for the figure to move side to side.
    the video helped but it didn't completely clear bout all my confusions about sorting.

    ReplyDelete
  24. engine room
    1. The code was easier to write when it was thought out before, since I was just following a layout I had already set up.
    2. I coded for a while in an online collaborative site (koding.com), and had to lay out my thoughts instead of just holding them in my head.

    ReplyDelete
  25. The process that I was unclear about was creating loops and actually understanding what I was doing.

    The videos helped my understanding of sorting

    ReplyDelete
  26. One concept I was unclear about was loops and with the ta's help I was able to understand it better.

    It helps me learn a method of sorting I was unfamiliar with.

    ReplyDelete
  27. 1.It didn't.
    2.It gave me a source of ideas/feedback.

    ReplyDelete
  28. I didn't understand "for loops", but I understand it a little better now

    Presenting helps to understand the pattern better. It also introduced me two sorting methods I wasn't aware of.

    ReplyDelete
  29. 1. Making a row of UFOs
    2. Yes, i understood it, though i do not think the dancing part was necessary.

    ReplyDelete
  30. I was unclear what we could use dictionaries for. But now I know, and knowing is half the battle. GOOOO JOEEE!

    N/A

    ReplyDelete
  31. 1.It made it so that the code was easier as I already envisioned it in my head

    2. I could collaborate with my partner making it easier to complete my code

    ReplyDelete
  32. 1. It helped me work out the details that I might have been confused about later
    2. My partner helped me to spot the places in my code that was causing my code to malfunction

    ReplyDelete
  33. After today, I think I understand for loops better. The explanation of the for loop flow was helpful, and I liked the problem we did where we monitored the values of x and y. My understanding of sorting grew from watching the video.

    ReplyDelete
  34. 1) Litterally not at all. I never used my paper once and completely forgot about it two minutes after coding.

    2) To be honest my partner wasn't much help (No offense if you're reading this). Asked questions and received mumbles in return. He also sort of left halfway through. He is not only to blame however, I didn't really give much initiative that i needed assistance.

    ReplyDelete
  35. Adris Jaoutakas (Ignore profile name)

    Engine room:
    1) It helped me estimate possible future problems in my code and saved a lot of time. It also was an easy way to understand the task at hand.

    2) Having a partner gave me somebody to explain and review the code processes. Other than that though, unfortunately partner work wasn't that useful for me today.

    ReplyDelete
  36. 1. Spending the time to write out a plan was helpful because it forced me to systematically plan my code before I started to write it.

    2. Working with a partner forced me to talk about and really understand what I was writing in my code which also helped me to be more precise with my code

    ReplyDelete
  37. 1. I was unclear with the speed to make my object move, but it's clear now with the TA's help. However I'm still confused with how the nested for loop works, so I just use two loops to make it easier to read.

    2. The way computer sorting is the same as how we sort our things. Computers just do it faster. It's still slow if it has to sort millions of data files because one file has to compare with the rest and check the values.

    ReplyDelete
  38. 1. Writing the plan helped me stay focused and understand the direction in which I was going.

    2. Working with a partner required me to know exactly what I wanted to do before I started writing.

    Random Sentences:
    referred to the house to know! Doodle-bug, doodle-bug, tell

    laid, as a chance at it all done."

    President; for a paper. He could not

    "Tom, why Tom's followed. Tom was jubilant.

    sun, and thought what boat and its slumbers and putting

    pride of the night of the mend--and then took

    "Stopped to the usual whisperings.

    boarded in it. He had changed hands. Sometimes his

    Terror of his adventure rose up, either.

    ragged one watching with blood." Tom's adventure


    ReplyDelete
  39. 1.It helped me prepare and create an outline of the program I was making, which allowed me to make changes to it and allow me to expand upon it when i actually wrote my program.
    2.Working with a partner changed my coding process since it allowed me to reflect on my work and allow me to double-check on parts of my code that might have been wrong. My partner helped me correct and modify my code.

    ReplyDelete
  40. Writing on paper
    Sped up the coding process
    Paper can be good.

    Working with a friend
    Whom I had worked with last year
    Was a lot of fun.

    ReplyDelete
  41. 1.The planning defintley accelerated my work, and allowed me to have a good idea of what I wanted to do, espescially functions and such before i coded them. The flowchart was invaluable in working through how to produce the code.
    2. Allowed us to hunt for bugs at the same time, and go over our debug etc, really sped up things in general and allowed us to check each others errors/mistakes etc

    ReplyDelete