First Assignment — CLI Game
My overall experience from developing a small game within two days was good. Although, I wouldn’t call it a ‘MVP’ (Minimal Viable Product) like we did. It was more like a ruff prototype.

Experience Gained
The assignment as a whole was a fantastic learning experience for me. I’m finally gaining a better understanding of why building and breaking programs are beneficial to learning. It allows me to understand why I would use a certain concept and how that concept actually works in practice. Compared to just reading about it from a book or website. Also, I’m able to mess around with it causing it to slowly meld into my MIND.
FINALLY!!!
Is how I kind of feel when I sort of understand something. Then go to try to use it and come to realize that I know nothing.
What I Thought
Two days are given for the assignment, which did not feel like enough time at all to plan to the extent that was explained within the criteria. However, even after planning; the amount of time remaining to build the ‘MVP’ of the product was enough time. That said, is only true if you took into account when planning the amount of time it would take to plan. Personally, I would change the criteria to have less planning so that students are able to create a product at a higher standard (I do understand that the course that I am currently undertaking is fast-tracked). This would allow for students to come up with an idea, implement enough for a prototype in a day and then build upon that during the second day.
Observations Of Class Sanity
This mainly was to do with the time constraint. Some people in the class decided to take on a project with a far larger scope than that of two days. The main perpetrator being Blake Doyle (needs link), really looked like he was contemplating being a landscaper. Similarly, James Luong Duong’s (needs link) sanity was rapidly evaporating. Minute by minute. This was something I found rather amusing, unfortunately.
