The Art of Subclassing

[@SpomenkoJabucar]

Raymond Hettinger - the man who decided to have a child to make his subclassing examples easier for us to understand.

[@karthickb1973]

😀

[@arunprasath9586]

Raymond Hettinger is a legend! You learn 10 times more watching him talk than reading a book!!

[@adamhendry945]

FYI, when he says the "Framework" pattern, this is actually the "Template" pattern in the original GoF book. The principle explained is correct, just the name is off. It's also referred to as the "Hollywood principle" (i.e. "Don't call us, we'll call you") or Inversion of Control (IoC) principle. Great talk!

[@salkdjfasldkfjsdlk]

Great video as always. You definitely changed my UML relationships from "inherits from" to "delegates to". Cheers

[@asmeurer]

Great talk. One thing that should be pointed out is that if you do want to subclass a built-in type like dict and avoid gotchas like __getitem__() not affecting get(), you can use abstract base classes from the standard library abc module, which take care of overriding all the methods for you.

[@joelcastellon9129]

I don't understand why python is presented as "easy" or "novice" language. If you come from the "status quo" of programming (Java, C++) you really have appreciate beautiful design of Python. I actually believe, doing serious coding in Python requires MUCH more care and thought than Java (from my experience).

[@liesdamnlies3372]

I completely agree. A long time ago I fiddled with Python for fun but I didn't really get much of anywhere. Now I'm returning to it, after having taken formal (i.e. in an actual college) Java and C++ courses, and holy fuck, it's beautiful. The decisions they made become a lot clearer once you have a better grasp of the "under the hood" logic that goes on in a computer. Python may be the epitome of "easy to learn, difficult to master".

[@yoyoyoyoyoyo907]

Great presentation. Very useful for someone coming from Java/C++ background. OOP in Python is quite different from what is being taught in today's CS curricula, this clears few things up.

[@jorgegimeno3869]

I really don't know why I didn't watch this earlier. A lot of the talks on classes in Python now make sense to me.

[@otter-pro]

Excellent talk. I learned a lot and I raised my hands at interval

[@pedlezelnip]

"The class with the most reusable code should be the top-most parent" I disagree. Part of the benefit of having a heirarchy match a taxonomy is knowledge transfer. By arguing that code reuse is the only metric that matters he misses one of the key benefits of OO thinking. He would argue that you need to "unlearn" that, but there's a cost associated with that he doesn't account for (my knowledge of the natural world I'm trying to model no longer applies to my code). This hurts readability ALOT.

[@matthewzeller5026]

This is awesome! Thank you.

[@sotirisf]

what does the man from the audience shout at 31:59 ??

[@davidedwards5069]

+sotirisf "Amen!"

[@sotirisf]

+Dave Edwards hahahaha thanks!!!

[@SalsaTiger83]

Your sentence structure hurts readability a lot. Taxonomic thinking is a convention in other languages. In Python, reusability trumps object orientation or taxonomy.

[@AlexanderArtemenko]

Boring. I've had much more fun from "Stop Writing Classes".

[@MMABeijing]

I know it's been a long time but that was a good one, thank you for that daily dose of sarcastic humor