Question

I’ve been reading about object oriented concepts, and I’m getting really lost.
Conceptually, all I understand is that a method “does” something and that a class is a “blueprint”. I’ve read all the analogies, but the only thing that really makes sense to me so far is:
Loops,if then, variable assignments, primitive data types, and the basic syntax.

To me, a program is a program is a program. You type in instructions, and the computer executes. I guess I don’t really see big picture.

Answer 1

The biggest part of OOP from a sky view, is organization and code reuse. You want to organize ‘objects’ that do a particular thing and you want to be able to reuse that for other applications as well. This idea just makes it easier to maintain what you are doing and where the information is and how it is all working together. This is very broad so let me know what you are truly not understanding.

Bundling code into individual software objects provides a number of benefits, including:

Modularity: The source code for an object can be written and maintained independently of the source code for other objects. Once created, an object can be easily passed around inside the system.
Information-hiding: By interacting only with an object's methods, the details of its internal implementation remain hidden from the outside world.
Code re-use: If an object already exists (perhaps written by another software developer), you can use that object in your program. This allows specialists to implement/test/debug complex, task-specific objects, which you can then trust to run in your own code.
Pluggability and debugging ease: If a particular object turns out to be problematic, you can simply remove it from your application and plug in a different object as its replacement. This is analogous to fixing mechanical problems in the real world. If a bolt breaks, you replace it, not the entire machine.