This hour marks a change from what we’ve been doing in the book thus far. Rather than learn about specific Scratch commands, this time around we’ll concern ourselves with documenting our Scratch project both privately and publicly.
What exactly does documentation mean from a software development standpoint? Why would we do it? Why is it important? By the end of this hour, you’ll know answers to all three of those questions.
In this hour will also tackle some related “meta-” programming topics as they relate to Scratch 2.0. We’ll examine the concepts of pseudocode and wireframing, two techniques that experienced programmers around the world use every day in software development.
Don’t be afraid: although I’m teaching ...