When you start learning about different paradigms, you’ll likely learn much more about inheritance when learning about the Object Oriented design paradigm.
To overly simplify, you create objects that inherit attributes from other objects. It’s for instance a way to create reusable patterns, that have stronger and more reliable data structures.
I made the joke comment, because for instance, you could create a Turtle class, and always know it was a Turtle. Again, an oversimplification.
If I could give a suggestion I wish I had gotten much earlier on in my education and career, it would be to really spend some time learning about the different paradigms, and their best use cases. You will likely ensure yourself a strong foundation in software architecture.
Just keep in mind that inheritance is nowadays a very contested feature. Even most people still invested in object oriented programming recognise that in hindsight inheritance was mostly a mistake. The industry as a whole is also making a shift to move more towards functional programming, in which object orientation as a whole is taking more of a backseat and inheritance specifically is not even supported anymore. So yeah, take the chance to learn, but be cautious before going into any one direction too deeply.
Yeah, I mix them too, although I apply quite a bit of functional techniques especially at the architectural level as well. OO I use mostly for dealing with I/O and other areas where statefulness cannot be avoided.
No one uses Boolean values anyway and with the amount of resources available on modern systems we can just replace them with integers and we should be fine. This also makes it easier to teach people, as they would learn less different data types.
I’m only commenting because the actual python is practically pseudo code:
# A turtle classclassTurtle:
shell=True# A boss classclassBoss:
authority=True#A class that inherits from anotherclassTigerTurtle(Turtle):
fuzzy=True# Multiple inheritance, or "The Devil's Playground"classTigerBossTurtle(TigerTurtle, Boss):
# shell, authority, and fuzzy are all true
...
I’m an amateur I’m not sure what inheritance is:X? Is it like instantiateing?
When you start learning about different paradigms, you’ll likely learn much more about inheritance when learning about the Object Oriented design paradigm.
To overly simplify, you create objects that inherit attributes from other objects. It’s for instance a way to create reusable patterns, that have stronger and more reliable data structures.
I made the joke comment, because for instance, you could create a
Turtleclass, and always know it was aTurtle. Again, an oversimplification.Oh yea, class resources. That would work! Thanks.im going to have to into this more, as it’s going to be useful
If I could give a suggestion I wish I had gotten much earlier on in my education and career, it would be to really spend some time learning about the different paradigms, and their best use cases. You will likely ensure yourself a strong foundation in software architecture.
Just keep in mind that inheritance is nowadays a very contested feature. Even most people still invested in object oriented programming recognise that in hindsight inheritance was mostly a mistake. The industry as a whole is also making a shift to move more towards functional programming, in which object orientation as a whole is taking more of a backseat and inheritance specifically is not even supported anymore. So yeah, take the chance to learn, but be cautious before going into any one direction too deeply.
I like to mix between OOP and FP for different levels. OOP is great for higher architectural problems. FP is great for everything under it.
And yes, inheritance was a huge mistake. Just use composition and interfaces instead.
Yeah, I mix them too, although I apply quite a bit of functional techniques especially at the architectural level as well. OO I use mostly for dealing with I/O and other areas where statefulness cannot be avoided.
If you’re interested, I also write an in-depth blog where I touch on these topics: https://arendjr.nl/blog/2024/07/post-architecture-premature-abstraction-is-the-root-of-all-evil/
At this point I think there is no software dev topic that is somehow not devisive.
Now I want to try something:
“Boolean variables don’t suck.”
No one uses Boolean values anyway and with the amount of resources available on modern systems we can just replace them with integers and we should be fine. This also makes it easier to teach people, as they would learn less different data types.
Yes I’m a software dev :)
I love it!
Inheritance established “is a” relationship between classes.
Underlying classes hold an inner object to the super class, everything from Turtle will be in TigerTurtle and BossTurtle.
In some languages that is configurable with public, private, protected keywords.
Relatedly, there’s also composition, which establishes a “has a” relationship:
Since Turtle is NOT a tail, but a whole animal, turtle should not inherit TurtleTail. But it HAS a tail, thus we add turtle tail as a property.
I’m only commenting because the actual python is practically pseudo code:
# A turtle class class Turtle: shell=True # A boss class class Boss: authority=True #A class that inherits from another class TigerTurtle(Turtle): fuzzy=True # Multiple inheritance, or "The Devil's Playground" class TigerBossTurtle(TigerTurtle, Boss): # shell, authority, and fuzzy are all true ...It is simpler than my faulty memory remembers, time to learn python again 😁