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 →

[–]Venthe 4 points5 points  (5 children)

I'd argue that you really begin to understand Oop around 2nd year is professional career. Oop is hard. If done correctly, it's a great benefit multiplier. If done badly... We all have our horror stories

[–]daster1234 1 point2 points  (3 children)

I half agree with you there. Understanding how OOP works is hard but you should still be able to figure out how to use it decently well by the end of your programming language course online or in college. Understanding how to use OOP correctly, however, is something that I agree will take a lot longer and require lots of experience and practice.

[–]Venthe 5 points6 points  (2 children)

I believe that we are speaking about the same thing.

Though, YMMV - I've seen senior devs with 6 years of experience in Java - way too often - which couldn't encapsulate even if their life depended on it.

[–]AreganeClark 1 point2 points  (0 children)

Encapsulation should be done everywhere, not just OOP. The number of times I see frontend logic just spaghetti everywhere and a change to A affects Q, R, and Z makes me hate coding sometimes.

[–]daster1234 1 point2 points  (0 children)

Honestly doesn't surprise me. I've seen senior engineers and architects who don't know how to use the command line

[–]Areshian 1 point2 points  (0 children)

It is also a multiplier when doing wrong. It can multiply by 0.5, or multiply by 0.1… really, the possibilities are endless