In this project, we were told to program a probability game to learn about coding and have it be displayed at our winter exhibition. I've done coding on my own before so I felt comfortable going into this project. To start this project, Dr. Drew gave us lessons in how to calculate probability through games such as "Pig". We were given lesson on how to use the coding program "Starlogo Nova". This was a new program to me and I was interested in learning how I worked. I worked alone for this project and created a "Plinko" game in the program called "Scratch". Since there was minimal time to create this game, I chose to work in Scratch because I felt that I would be producing a better quality game in a program I had already learned. After exhibition, we looked at probability in other areas such as in statistics and percentages.
For this project we had many benchmarks. The first benchmark was a brain storming sheet. We were instructed to create a vision board of what we wanted our game to entail of. We also got to decide if we wanted to work alone or with a partner. Feeling pretty comfortable with coding, I thought it would be best to work by myself. The second benchmark was the proposition of your game to Dr. Drew. I proposed my idea to Dr. Drew and he said that it could be an easy game to make but there were a few tricky components that could set me back. I thought about it for a while and still went with my original idea. One of the last benchmarks was the actual game. I spent a lot of time making my game because I wanted to create something that could engage my audience both young and older. I think that my game was successful because I got a lot of good feedback during exhibition.
Wait for the ball to get to the bottom and your score should appear on the top
Reflection
I felt very comfortable with my game. I was really proud of how it turned out. I was happy I stuck with my original idea. There were obstacles such as the codes not complying with the rest of the game. I learned how to take my time in order to make something I was proud of. The two Habits of a Mathematician I used were "Starting Small" and "Looking for Patterns". For starting small, I wrote out each part of my code individually in order to not get confused. This benefitted me because I was able to go back and look at my mistakes and know where I went wrong. I looked for patterns when writing my code because I knew a lot of the actions would have the same code written. If I could go back during this project, I would space it out more because it would have saved me a lot of trial and error time.