Arrange tutorials by primitives and identify holes in concepts

[joeldart]

If we look at our activity for girls inc, we are able to accomplish the entire game through a small number of programming concepts:

• loops
• ifs
• variables
• (if you make it to the step) random numbers
• (if you make it to the final step) prototypes/constructors

There are likewise, several scratch concepts that get introduced:

• movement
• rotation
• collision detection
• multiple sprites
• changing backdrops

Other concepts further build upon the simpler programming concepts:

• abstractions
• functions
• iteration
• mapping
• reduce
• algorithms
• events
• message bus/pubsub
• code clarity
• refactoring
• DRY
• etc

It would be good to

1. arrange tutorials in such a way that these higher level concepts are introduced
2. identify concepts we are missing and add issues to create these
3. create Mozilla Open Badges for the concepts

For example, jon started to write in refactoring into the breakout tutorial. Lets instead pull that out into the "quick and dirty breakout" and the "refactoring breakout" and the "making lots of blocks with clones breakout." So then we can assign badges to each tutorial too.

This can also help us identify areas where we're weak, for example, we have no "functions in scratch" tutorial despite it being a feature for years now.