You have made a good point about the disadvantage of following other code that could limit your thoughts, and sometimes it is not easy to follow someone else logic and flow. But I do have some reflections on this. First, code is not a neutral practice that embodies human experience, knowledge, as well as ideologies. Although two approaches can work toward the same result, how people structure and write code can be very different. Through your close reading of code, you start to question why a program has to be structured in a particular way etc. Then you make follow up action to change your own code. In this way, reading code can be seen as a critical exercise to push yourself to think why they are appeared in this particular way and how may it contradicts with my own thoughts. My question would be how do you see the similarity of reading code and reading text? Or how may we use this 'reading code' strategy to examine wider cultural system? (this is more a software studies question)
In relation to your flow chart, it would be great to somehow indicate the key code in navigating your game. For example, listening for player input with the space button. In addition, the flip physics part can be something expanded upon to show the logic of when it will flip. The flow chart right now is easy to read but it seems over simplified some of the logics that are important as part of your game logic.
You have made a good point about the disadvantage of following other code that could limit your thoughts, and sometimes it is not easy to follow someone else logic and flow. But I do have some reflections on this. First, code is not a neutral practice that embodies human experience, knowledge, as well as ideologies. Although two approaches can work toward the same result, how people structure and write code can be very different. Through your close reading of code, you start to question why a program has to be structured in a particular way etc. Then you make follow up action to change your own code. In this way, reading code can be seen as a critical exercise to push yourself to think why they are appeared in this particular way and how may it contradicts with my own thoughts. My question would be how do you see the similarity of reading code and reading text? Or how may we use this 'reading code' strategy to examine wider cultural system? (this is more a software studies question)
In relation to your flow chart, it would be great to somehow indicate the key code in navigating your game. For example, listening for player input with the space button. In addition, the flip physics part can be something expanded upon to show the logic of when it will flip. The flow chart right now is easy to read but it seems over simplified some of the logics that are important as part of your game logic.