Should I keep practicing OOP or move on to building real C# projects?

Don’t expect OOP to suddenly become obvious just because you read more theory. It also doesn’t always need to dominate every C# program, since the language supports several programming styles. Learn the fundamentals, then build projects and revisit the concepts as real problems appear. You can understand the mechanics now and develop better design judgment gradually through practice.

A useful way to design a class is to start by asking what its responsibility is. What job does it perform, what data does it own, and what information should it provide to other parts of the program? Sketching the relationships between objects can help. If several objects repeatedly handle the same data or behavior, that may suggest a separate class or shared abstraction. OOP is largely about dividing responsibilities clearly and keeping the code modular, not memorizing a list of principles.

Try extending your banking project instead of studying OOP only through generic Animal and Car examples. For instance, you could have a base Account type with shared behavior, then separate account types with their own rules. A child account might restrict credit or require an extra verification step when withdrawing, while a regular account could allow those operations. This shows how shared behavior, specialized behavior, inheritance, and overriding fit together in a realistic setting. Just avoid creating inheritance merely for its own sake; use it when the types truly represent variations of the same concept.

Move forward and start building something small that genuinely interests you. Many OOP ideas only become clear when you encounter a real design problem in a project. A desktop or web app will give you more useful practice than repeating another artificial console exercise, and you can return to specific concepts when you need them.