Prefer a written version? There is a visually-explained post on my blog: acairns.co.uk/posts/composition-over-inheritance Disagree? Got feedback? Let me know below, or jump on Discord: acairns.co.uk/discord
As a non coder working with visual scripting languages I have been discovering these concepts by myself, and it's quite rewarding to see my suspisions confirmed by someone more knowledgable
Unfortunately I haven't reached the dizzying heights RUclips have set for monetisation and can't control when the ads show 😢 One day, maybe... Glad you enjoyed it, though!
first time watching one of your videos, and honestly im impressed. I hope this goes well for you so that i can enjoy these videos in the fututre and so that you can improve even more the quality.
Refreshing to hear real world advice, rather than the usual "always do this" nonsense. Just because a toolset has a tool, doesn't mean should or shouldn't use it. Tools are not good or bad by themselves, but using a hammer for a screw is a bad idea. Great content
Thanks Dave, Glad you enjoyed the video! Nothing is black and white - just lots of different shades of grey in different contexts. It's our jobs as engineers to understand the tradeoffs and make the best decision with the information we have. Also, I just recently used the hammer/nail metaphor in an article! 🤣 acairns.co.uk/posts/primitive-obsession
@@metaphoricallyspeaking I do think there’s a market for accessible and engaging explanations of software engineering concepts. Looks like you’ve got it nailed down. Instantly subscribed!
@@metaphoricallyspeaking the combination of your voice, your visual style and the fact that you’re covering not beginner but intermediate topics make me look forward to you future videos!
haven't watched the video yet, just wanted to say I (a 20yr veteran programmer) just learned about the concept a few weeks ago, though I've been an unknown advocate and practitioner of composition since being introduced to requisite oop in Java in high-school. I've carried the notion through all my projects since. always thought inheritance was a bad idea outside of strict polymorphic virtual functors where you can leverage the compiler to produce code states nessesary vs boilerplate every time a new instance is found. templating in c++ does exactly this for functional and procedural bros ok, watched the video. that last sentence "use inheritance when it exists in that domain" is basically saying the same thing. nothing in the real world actually does this. the nature of reality is to have many close but independently unique variants with- at best- partial heredity on average due to the imperfect copy problem. practically nothing is perfectly all of one other thing plus new stuff.
I don't like the fact that this video misses the importance of interfaces and polymorphism which are solutions to most of the inheritance problems that the video talks about. I honestly think that if you're going to make any kind of program and you're being smart about you program's architecture, you will inevitable use both.
That's fair. Polymorphism is certainly important. The video aimed to demonstrate how composition can address specific problems associated with inheritance. Hopefully I didn't imply it's the only necessary paradigm.
Prefer a written version? There is a visually-explained post on my blog:
acairns.co.uk/posts/composition-over-inheritance
Disagree? Got feedback? Let me know below, or jump on Discord: acairns.co.uk/discord
Whoa. The "has a" vs "is a" statement flipped the missing switch in my brain. You rock brother.
Thank you - glad I could help you build a mental model of Composition over Inheritance! 💪
Fantastic video! Loved the design, graphics, editing and relatable gaming analogies throughout. Honestly, top work!
Much appreciated - glad you enjoyed it! :D
As a non coder working with visual scripting languages I have been discovering these concepts by myself, and it's quite rewarding to see my suspisions confirmed by someone more knowledgable
Amazing. Thanks for sharing!
this video has so much style, I love it, keep up the good work ;)
Thanks Kari, appreciate it. Will try! 😅
Love the style for sure! The ad threw me for a loop though. I thought I had click out of the video by accident.
Unfortunately I haven't reached the dizzying heights RUclips have set for monetisation and can't control when the ads show 😢
One day, maybe...
Glad you enjoyed it, though!
I really enjoyed this one, especially the animation. Great work.
Thank you Stephen. Glad you enjoyed it!!
This was such a cool and beautiful video! I'm probably gonna binge all your videos when I get back from work later
Thank you. Hope you enjoy - new video is almost done, too!
Fantastic production quality and excellent teaching skills. Great work 👏👏
Thanks for the kind words, Bob - glad you enjoyed it! 😊
first time watching one of your videos, and honestly im impressed. I hope this goes well for you so that i can enjoy these videos in the fututre and so that you can improve even more the quality.
Thank you so much for the encouragement Tobias!
5:07 - oh yes, bonus point for you and scott
Scott is incredible. And his cinematography is at such a high standard. His drawer organiser video made me impulse-purchase a 3d printer.
That's a great video, nice explanation and incredible visuals ! Thanks for sharing you amazing work
Thank you! Glad you liked it!
Very interesting insights, keep it up! Subscribed.
Thank you. I'll try! 😅 Welcome aboard! 😁
Refreshing to hear real world advice, rather than the usual "always do this" nonsense. Just because a toolset has a tool, doesn't mean should or shouldn't use it. Tools are not good or bad by themselves, but using a hammer for a screw is a bad idea.
Great content
Thanks Dave, Glad you enjoyed the video!
Nothing is black and white - just lots of different shades of grey in different contexts. It's our jobs as engineers to understand the tradeoffs and make the best decision with the information we have.
Also, I just recently used the hammer/nail metaphor in an article! 🤣
acairns.co.uk/posts/primitive-obsession
SuperMario is a Mario.
Mario: It's a me?
It's a you! 😆
Amazing explanation
Thanks Steve - glad you liked it!
The graphic design is crazy. Easy sub earn
Awesome. Really glad you enjoyed it! :)
Nice explanation.
Glad you liked it :)
This is amazing stuff!
Thank you! ☺️
@@metaphoricallyspeaking I do think there’s a market for accessible and engaging explanations of software engineering concepts. Looks like you’ve got it nailed down. Instantly subscribed!
@@pindab0ter Thank you. Thanks for the kind words! :D
Not nailed down at all, I'm afraid. Learning a lot as I go! Haha
@@metaphoricallyspeaking the combination of your voice, your visual style and the fact that you’re covering not beginner but intermediate topics make me look forward to you future videos!
@ThePrimeTimeagen We need your reaction. Primeagen approved or nah?
This was a great video @metaphoricallyspeaking. Keep up the great work!
I would be proud and terrified - in equal measures!
But, if he were to roast the video, at least I could take the low-road and mock his hair! 😁
Appreciate the kind words. Will certainly try! :)
haven't watched the video yet, just wanted to say I (a 20yr veteran programmer) just learned about the concept a few weeks ago, though I've been an unknown advocate and practitioner of composition since being introduced to requisite oop in Java in high-school. I've carried the notion through all my projects since.
always thought inheritance was a bad idea outside of strict polymorphic virtual functors where you can leverage the compiler to produce code states nessesary vs boilerplate every time a new instance is found. templating in c++ does exactly this for functional and procedural bros
ok, watched the video. that last sentence "use inheritance when it exists in that domain" is basically saying the same thing. nothing in the real world actually does this. the nature of reality is to have many close but independently unique variants with- at best- partial heredity on average due to the imperfect copy problem. practically nothing is perfectly all of one other thing plus new stuff.
Super detailed reply. Appreciate you sharing your perspective! 🙌
Nice. Subscribed.
Appreciate it 🙌
2:42
int player_state = 1 // 2, 3, 100, 102020
no inheritance, just pure states )))
Sometimes we might not want to merge all logic into a single class and toggle based on the state
@@metaphoricallyspeaking so basically separate the states into separate scripts?
I don't like the fact that this video misses the importance of interfaces and polymorphism which are solutions to most of the inheritance problems that the video talks about. I honestly think that if you're going to make any kind of program and you're being smart about you program's architecture, you will inevitable use both.
That's fair. Polymorphism is certainly important. The video aimed to demonstrate how composition can address specific problems associated with inheritance. Hopefully I didn't imply it's the only necessary paradigm.
@@metaphoricallyspeaking No not at all, the video was great! I just felt like it was a bit unfair for inheritance hahah
@@RUEDO123 hey do you have any resources on polymorphism and how do use interface ... ?
@@anand_- No but it's pretty easy to find them with a google search
@@anand_- not at the top of my head, but I'm sure there are videos and tutorials explaining the concepts