pezdispenser dispenser

Think of the class Pezdispenser (where the code is), as a blueprint of a house. It is not able to house a family while it is just a blueprint, so you get a construction company to build the house according to the blueprint. The constructed house is now an object, and can do what it is supposed to do. A family can now move in there. Then another family wants to move in to a house. They can't move in to the already created one, a family is already living there! So they call the construction company and builds a new house.

This is also what's going on with the Pezdispenser. It's a class you have to create different pezdispensers, because maybe just one isn't enough. When you type Pezdispenser dispenser, you are giving it a reference name, a way to know which of the pezdispensers you are actually talking about. For instance, one may be called casparsDispenser, and another anderssDispenser.

To break it down. This is how you could construct a Pezdispenser:
Pezdispenser dispenser = new Pezdispenser("Yoda");
_____^_________ ^ _____ ^ _________ ^ __________________
(type/class) ___ (name) (new) (the types construction company, and your personal touch (Yoda))

You can't call it simply Pezdispenser because there may be a multitude of different objects of that class. You have an object already and you named it dispenser. There are cases where there are not expected to be a multitude of objects of a class (this is also called instances of that class), so in those cases you dont have to write something like Pezdispenser dispenser because you don't need to distinguish it from other objects.

Hm, did any of that make sense? Good luck!