You're listening to coding blocks episode one.

I'm Joe Zach and I'm Michael Outlaw and I'm Alan Underwood and this is the show where we'll be discussing various programming topics, our pains,

our gains, tips, tricks, and etc.

Today we're going to be talking about interfaces.

What they are, why to use them, the good, and the ugly so let's start off with the first thing right

interview question number one what what's an interface basically you look at them as a

contract of what you what you have to adhere to when you're programming.

If there's something in the interface, then you have to make it do something, or you have to at

least put some code to it so that it fulfills that contract.

Yeah, so I think it was like guardrails on the highway, so the interface defines how you

should be using the class in that context.

Or that piece of data, you're defining like how you should use that piece of data you're defining like how you should use that piece of

data how you should interact with that piece of memory at runtime but not

necessarily you know giving them the keys to the castle. Yeah, I want to, I mean this stuff's here, the landscape's there.

There's other stuff you can do with this class, but if you want to do something that's off the road,

then you should talk to the person who did it.

Yeah or even I mean that's one way you think of it but also another way to

think of it is like if you want to use this as this right I'm trying to think

of like an example like an an I innumerable right or I list but

depending on how you want to use it then you can use it as that or you can use it as

this if your class implements multiple interfaces maybe?

Yeah, I like that.

...