This was one of the first complex projects I ever made in Scratch. If you look at the monkey’s code you can see that it’s pretty tricky to work out quite what’s going on. There are lots and lots of scripts, some of which are almost exactly the same. The sprites’ names have been left as the default ‘Sprite1’, ‘Sprite2’ etc, so when you try to read the scripts it’s difficult to work out what they do. There are loops within loops within loops, which often makes them hard to make sense of. When I made this project I had a good sense of the logic of programming in Scratch, but I hadn’t thought about which approaches would be most helpful if I were writing code as part of a team, or if I wanted to reduce the processing power of a computer. Very few people do learn to program with these factors in mind, and yet if we learn about them earlier we can pick up good habits, collaborate more easily, and make the job of creating with technology an easier and more satisfying process.
Find the next version of the project here: https://scratch.mit.edu/projects/322219873
