[Help] OOP - Better understanding

Question

Hello community,
I have learned c# over the years, but I still have a hard time to fully grasp the architectural side behind OOP.
In my case in bigger projects, I always end up with classes which have too many dependencies on each other and other design flaws.
That's pretty odd and doesn't scale well.
How did you guys fully get the implementation or correct mindset to build projects in a scalable and efficient way?

Answer 1

Do not think from a functional program perspective. Think of it as each individual object.

What is the object?
What should the object have?

For example, Person is an object.
It should have properties such as name, date-of-birth, gender, address and so on.

Yes, a Person can have a Car. And Car is another object with its own properties.

A bit similar to database table relationship. If you can grasp that, you should be able to understand OOP.