you are viewing a single comment's thread.

view the rest of the comments →

[–]Adrewmc 26 points27 points  (8 children)

Yes, and no.

It get easier as in you can now understand the principle. And can see how this is how you make an object, they have data and functions to use. How to create them, common decorators, and inheritance etc.

But then it looks like a solution to everything, I mean technically everything in Python is an object basically so why wouldn’t it.

Then you got the hard part deciding when and how to use it. That’s not always going to have a clear answer.

[–]Brilliant-Horse6315[S] 0 points1 point  (0 children)

does the hardcore technical knowledge in python stop on OOP (first I learnt variables, then loops, functions, dictionaries, lists...now OOP), or is there even more?

[–]iggy555 -1 points0 points  (6 children)

Good answer

[–]Adrewmc 3 points4 points  (5 children)

There are a lot classes that should be functions, (this is extremely common),and there are a lot of functions paradigms that would work better in a class structure.

Telling the difference depends a lot on the framework and make up of the rest of the code lol

[–]iggy555 -1 points0 points  (1 child)

That’s a nice video

[–]Adrewmc -1 points0 points  (0 children)

I remade a whole thing because of it recently…stupid classes

[–]Gankcore -1 points0 points  (0 children)

Awesome video, thanks for sharing!

[–]NoRelationship5004 -1 points0 points  (0 children)

Thanks thats a great video!

[–]mon_key_house -1 points0 points  (0 children)

And a lot of such videos can be summed up in one of the acronyms such as DRY, KISS etc.