Much of the "OO" code you see is procedural. I have already committed and continue committing several "sins" per day by programming OO.
The paradigm is not easy to learn and takes time, meanwhile several errors are committed and the code's maintainability suffers. When you leave college you are just a creator of chaos, which over time can develop the ability to create and restore order in the projects you are involved in.
But if cake recipe was available ...
Does it exist? If it exists, what is it?
What would a well-designed OO study consist of?
For example, in my learning I really needed to know Liskov's replacement. Tell do not ask was also a mind opener (create getters ) only where necessary and have the object execute the action instead of asking for the required information and running from outside). Design patterns I'm getting acquainted with, and I'm studying UML too (since there is no A & OOP book that does not apply). The whole technique of creating domain models is interesting because it helps me choose the right objects to be placed in the domain rather than by inventing random abstractions. Other things are important too, cohesion, coupling.
These are "snares" that I wish I had avoided if they had been passed on to me previously. So the question.
Or leave all this and go sell coconut on the beach? (rhetorical question:).
EDIT : I've changed the question to make it more objective, but do not mess around with the original content.