generated from mwc/lab_retro
f8606a776c
games. When I work through this format of coding it seems much more linear and easier to troubleshoot. I think back to my drawing project and every part of the process was housed in the one page of code without the use of classes at all. If I had understood classes, I could have broken up the pieces of the books that iterate into a class. The I could have used that class to complie the image itself. It makes the creation of the code and program cleaner as well. Everything is in the same spot on each page. So, when there is an error, or something does not look quite right, it is simple to find the thing that needs to be fixed and troubleshoot it. Without that the process would be hunting for the location of the problem then trying to decipher the fix. When thinking about students interacting with programs and the process of learning computer science, organization like this makes things much more accessible. Problems are easy to find and work through. It also makes grading and feedback easier to give (as a techer) since the code itself can be graded on coherence as well as effectivness. |
||
|---|---|---|
| __pycache__ | ||
| .commit_template | ||
| asteroid.py | ||
| asteroid_spawner.py | ||
| nav_game.py | ||
| poetry.lock | ||
| pyproject.toml | ||
| spaceship.py | ||