[MUSIC]
Welcome back.
Last time we met, we talked about the importance of making a design document for
your game, a document that collects your thoughts and descriptions of your games,
so we can describe it and share it with other people.
We also had some homework for the week.
We made a simple game just to get us started.
We collected our game with a short description and a few instructions, and we
shared it with our friends and classmates to get their reactions and their feedback.
In putting your game together with a description,
you are actually making a simple design document.
Remember, from last week?
A design document, it has no standard format, but it has a standard purpose.
It communicates your game, and your homework did just that.
So why when I gave the assignment, did I tell you to make a game and
not a design document?
Well, I thought if I called it a game, it would be more fun.
If I called it a design document, which can some times be these giant books
that take tons of time to create, some of you might have been intimated.
You might have tried to pack too many things into the assignment,
and it might have become something that wasn't possible to make in one week.
Calling something a game, and thinking of something as a game keeps it fun.
Thinking creatively is much easier when we're at ease and enjoying our time.
It's important while we create, that we should be having fun and
playing with our ideas.
And that's why, in these lectures, sometimes I talk to a puppet.
>> I'm a puppet.