The way 'inheritance' works in object-oriented programming

Coding is mostly just a clever way to be lazy. Inheritance is the ultimate hand-me-down system, saving us from the absolute faff of rewriting the same instructions over and over.

Imagine a master recipe for a basic sponge cake. Instead of listing flour, eggs, and sugar for every new treat, a Lemon Cake simply inherits that base and adds its own zest.

The child class grabs all the parent's traits for free. It is wonderfully efficient, but it means if the parent recipe is a disaster, the whole family tree is in trouble.

Wait, can the child cake just ignore the bits that are a mess?

Oh, you absolutely can! In the coding world, we call that 'overriding.' It’s like inheriting your grandmother’s dusty old drapes but deciding to dye them a vibrant teal instead.

The child class basically says, 'Thanks for the base, but I’ll handle this specific part myself.' It keeps the flour and eggs but swaps out the cooking time or the sugar ratio.

It’s like a seaside holiday where everyone stays in the same cottage, but you’re the only one who refuses to wake up at dawn. You’re still part of the family, just with better boundaries.

But does dyeing my drapes teal change them in grandmother's house too?

Not at all! That’s the beauty of it. You aren’t actually touching the original drapes in grandmother’s parlor; you’ve essentially taken a carbon copy of the pattern and made it your own.

In coding, your 'overrides' only live within your specific child class. The master recipe stays tucked away in the cupboard, completely untouched by your experimental zest or any other 'faff' you've added.

It’s a relief, really. It means you can be as rebellious as you like without causing a scandal or breaking the code for everyone else.

How does the computer know which version of the recipe to follow?

It’s all about the address. When you ask for 'Lemon Cake,' the computer looks at your specific instructions first. It’s like a guest who checks your room for those teal drapes before wandering into grandmother’s parlor.

If it finds your custom version, it stops and starts baking. It only trudges to the master cupboard if your specific class hasn't mentioned that step at all.

This 'lookup' saves the computer the faff of searching everywhere, ensuring your rebellious choices get the spotlight while the originals stay tucked away as a backup.

So what happens if the guest finds no recipe anywhere at all?

If the computer reaches the very top of the family tree and still finds nothing, it doesn’t just wing it. It throws a tantrum, which we politely call a 'Runtime Error.'

It’s like tearing the seaside cottage apart for the kettle, only to realize there isn't one. The holiday stops because you can't have tea. What a faff!

Every family tree eventually leads back to a 'Grand-Ancestor' object. If even that old soul doesn't recognize the command, the computer gives up and sends a grumpy message.