It's a keyword in OOP languages like Java etc.

Sure, I think this one is Dracula

Hey! Thank you for the kind feedback and the suggestions. Comments like these really help me to determine what type of content you all want to see. Thanks for watching 🙂

That’s because it is dependency injection 😉

I think you can get a more complete picture if you also watch my video on interfaces: kzfaq.info/get/bejne/f8iIhqh4p56wgqc.html

Watched it and it makes sense to me but I'd imagine any newer users wouldn't be able to follow all that since it requires understanding of databases/databases connections. I feel like this video could have been better with a second thing to demonstrate the flexibility of interfaces over functions for abstraction. For the vending machine example it still seems like a regular function would have been better choice to avoid all that boilerplate.

@@kevinb1594 it actually doesn’t require understanding of db/db connections since all of the db stuff in that video is “abstracted”. That’s the point. Back on the subject of this video. The point of this video is to teach abstraction. We use the interface to define the contract. If we just use regular functions there is no boundary first of all, not to mention the code that is “abstracted” will become tightly coupled with the code that uses the methods if we remove the interface like you suggest. The above point I explain in the video but since this is a rather complicated topic… I’d suggest watching the video multiple times if you aren’t fully understanding it 😊

@@kantancoding I guess it depends on what level of 'new' someone is. I was thinking about folks who have never actually looked into databases at all. They would have no idea that different databases have different underlying mechanisms and requirements for connecting/querying but I guess that is the hard part of teaching, you never know what gaps someone has and those of us with the knowledge/experience take these small details for granted. With that said, I appreciate the content and the effort you're putting into making these videos. Not sure if I've been rekt by JS and functional programming because I've always struggled to wrap my head around OOP concepts.

I’m actually not taking those small details for granted. Leaving out details about database is intentional since like I mentioned before, you don’t need to understand that stuff to understand the topic of that video which is interfaces. Not to mention, going over database stuff will just convolute the explanation of interfaces. If you are stuck on the database stuff just replace database in your mind with something else. For example, sticking with the audio interface example I used to explain, imagine that there are multiple different microphone brands/models that you want to connect to the application. And the interface method is getSound(). As long as all of the microphones implement the method to getSound() defined in the interface.. they can connect to the app. As you can see it’s the exact same example without the databases . That’s why I’m saying the database stuff is irrelevant and therefore isn’t something that you need to understand to understand the topic of that video which is interfaces. Now back on the subject of this video. If you still can’t grasp abstraction and why I used an interface in this video, don’t get too discouraged. It is a bit of an advanced topic. Just keep trying to understand and eventually it will click. Also, nobody with extensive “knowledge/experience” is watching these videos and there’s also nothing to prove here. So you don’t need to justify your lack of understanding oop concepts or anything else. The important thing is you are actively learning 👍🙂 Anyways thanks for supporting! Hope you come to an understanding soon!