OOP - Objected Oriented Programming

Fortunately this course was not my first time tackling OOP. I learned Java in high school, and while I didn't fully grasp the concept of OOP at the time, I was able to follow along. However, this prior experience was a great help in understanding it this time around, because some parts were review, and gaps I had before were filled with concepts I learned now.
OOP revolves around classes. As far as I can tell, this makes it easier for everyone that interacts with the code. The ability to just spawn a child class which inherits all properties and methods from the super class makes it convenient and easier to add on to programs. I guess this follows 2 of the 3 'principals' that Prof. Heap was talking about(Laziness, Impatience, Arrogance).
Thinking of classes as blueprints is perhaps what made them the easiest for me to understand. It's real easy to figure out the real world applications when I think of it in this way. Employees, Students, food items at fast food restaurants; they're all just instances of classes with a variety of attributes tied to them.
In order to back up my understanding of the concept I jumped on codecademy.com and played around with their exercise that had to do with classes. I find this practice invaluable as it helps me discover common low-level mistakes that I make, so I can avoid making them in tests/exams.