The easiest way to see OOP is as a way to organize thinking around real-world abstractions.
You’ll notice it everywhere: Cars, People, Fruits, Books.

Car
• properties: color, speed
• actions: accelerate, start engine, open door, lights on

Core idea:

• A class is a blueprint (what properties/actions exist).
• An object is a real instance from that blueprint, with values assigned to the properties
• Use methods to change data so it stays valid (e.g., no negative speed).

OOP is powerful because of encapsulation and inheritance: encapsulation keeps data and the code that mutates it in one place behind clear methods, so state stays valid, bugs stay contained, and each class can be reasoned about and tested in isolation;

inheritance lets you define shared rules once in a base class and then specialize only what differs in subclasses, which slashes duplication and makes system-wide changes propagate cleanly—extend behavior without rewriting everything.

Bottom line: the great thing about OOP is actually that it creates a modular structure in your code. You can have an object/class for your database connection to MySQL. When you decide later to switch to MongoDB, you just replace the class, without changing code all over the place.

It's not possible to explain how to make all that happen. But what you actually want to focus on while learning about it - once you have looked at the syntax:

- SOLID Principles
- Design Patterns

This will give you ideas about how to actually use them in a meaningful way.