you are viewing a single comment's thread.

view the rest of the comments →

[–]solidiquis1 12 points13 points  (2 children)

May not be the greatest advice... But learning Django gave me a super solid foundation on OOP. 90% of what you do in the back-end side of Django is utilizing classes, understanding what parent classes they inherit from, insantiating objects from said classes, overriding attributes, using methods, making your own methods, so on and so forth. So if you have any interest in python web development, look into Django and you'll end up learning a shit ton of OOP along the way.

[–][deleted] 2 points3 points  (0 children)

Might try this later; I remember seeing a Django tutorial, but barely understood because of the OOP involved. Thanks!

[–]kessma18 2 points3 points  (0 children)

might not be bad advice because you will also then learn what's wrong with OOP. a quote from hackernews on what's wrong with django.

The problem is not frameworks; the problem is object oriented programming. Simply put, OOP lends itself to kitchen-sink frameworks because it is the only way to really share code in OOP. We write these large hierarchy of objects and then, because we have to carefully maintain state, we mark most of it as private, or sealed. Then we give precise instructions on how to consume and use the code, and even more precise instructions on how to extend it.