Quiz: what does the sprite say when each script is run?

Correct!

Not quite! Check your truth tables.

Sorry! Check your truth tables, or try running the script.

Correct.

Correct!

Not quite! Make sure to keep track of the values of your variables.

Correct!

Not quite! Make sure to keep track of the values of your variables.

Correct! That was a nasty one, wasn't it? Soon, we'll learn how to use abstraction to make things cleaner.

Not quite! Make sure to evaluate innermost blocks first.

Nope! Try running the script!

Yes! This wasn't what you expected, was it? The problem here is that only knows how to deal with boolean (true or false) inputs. Since x and y are numbers, doesn't know what to report (4 or 5 doesn't really make sense).

Correct! Here, we made sure that the only inputs to or were booleans.

Nope! Try running the code.

One thing you should notice in the above questions is our method of naming variables. To keep things in order, it is a good idea to choose variable names that give us an idea of their function. In particular, when we have variables that keep track of boolean values, we give them names that sound like questions. For example, the name of the variable "inCalifornia" reminds the programmer that the variable will only contain true or false (because "Are we in California?" is a yes/no question). You can even add a question mark to the names of your variables if you like (e.g. "inCalifornia?").