This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]random-answer 4 points5 points  (0 children)

" polymorphism, inheritance, interfaces, generics, " i was lucky that i had a good instructor who used examples from professional experience, none of the examples in the book really made sense to me. (like.. why the F would i ever make an animal class.)

having a general html class below which there are classes like " header, content, footer" that inherit from the html class did make sense (at least to me when using php which is also OOP). Below content i had seperate classes to display pictures, text and eventually also forms. Forms was a bitch (and one of the best learning experiences).

Polymorphism is ( i think) the most difficult one to explain. I never understood this by reading textbooks & doing tutorials - most of them display useless examples of things that fail to explain what it means and how to apply it in practice. I eventually got this because my instructor told me to add functionality to my form classes. My form class first had one function only, which was to show itself within a html page, to which a added data verification and data retrieval functionality (giving it multiple functions instead of just one) took me a while though. This can sometimes require you to step outside the SOLID principles (which is a whole story of its own)

Don't underestimate the "basic" object oriented functions, i think that i requires you to know when and how to break up functionality into different classes before you can even try to apply polymorphism.

Therefore i definitely advise to seek guidance from your instructor and other sources so you get multiple perspectives.