Fundamental Concepts of Object Oriented Programming

[@dariusz.9119]

"An employee of a business is also a person" - that's a bold statement right there

[@ComputerScienceLessons]

That's what I keep telling myself! :)KD

[@beltusbenz6911]

exactly ! very outlandish .

[@Wida85]

😂😂

[@anointingdaniel216]

For real 🤣

[@renren_27]

🤣🤣🤯

[@laurastephenson5169]

I'm a university professor myself, and I have to say that is the most crystal clear, explanation I've ever seen for computer science concepts.

[@ComputerScienceLessons]

Delighted to help. Thank you :)KD

[@MatthewTipton2]

Absolutely brilliant. Simple, clear, concise. The whole concept in my mind started as a soft blur and sharpened to crystal clarity.

[@trevoro.9731]

A lot of BS actually, the author didn't pay attention to correct definitions. But useful to find out common misconceptions.

[@darianxd5508]

why is it BS?@@trevoro.9731

[@notyournormaldev1419]

The clarity and simplicity is unparalleled.

[@ComputerScienceLessons]

Thank you :)KD

[@SithLord2066]

So you're saying it's serial? Since it's not parallel

[@notyournormaldev1419]

@@SithLord2066 lame.

[@SithLord2066]

@@notyournormaldev1419 I'll be here all week

[@benediktkraas8576]

Probably the most useful 10 min of learning OOP so far. I never really understood those 4 principles and now they seem a) sorta easy (both to use and memorize) and b) I was already applying some of them without knowing. Amazing! Thank you kindly

[@sandrakyoutube]

Remarkable. Remarkable simplicity, clarity, and conciseness. Transformed my vague understanding into clarity without overwhelming me. Thank you!

[@ComputerScienceLessons]

You are most welcome. Thanks for the lovely comment :)KD

[@toolittletoolate3917]

OOP was THE hot topic when I was a developer. Took me a little study to understand its foundational concepts. I couldn’t understand why everyone seemed to think that it was THE way to create programs. Sanity eventually prevailed, as it usually does, and it certainly has its place, but if your design does not utilize inheritance and polymorphism, then use another language type. Don’t force a particular model into an OOP design just because your CompSci instructor loved Java.

[@SnakeEngine]

You can do (real) OOP in C, and do it better than in Java.

[@Ahmad_Al-Deeb]

"Encapsulation: Data and the programs that manipulate those data are bound together and *their complexity is hidden*." This part was useful since I thought encapsulation is just about bundling related properties & methods together and was missing the fact that it reduce complexity also by hiding data which is a little similar to Abstraction hiding implementation details. Thanks!

[@ComputerScienceLessons]

You're welcome. Glad to help :)KD

[@hunterjiang5894]

This video is the most helpful and concise one I 've ever seen so far among those about the fundamental terms and concepts. Thanks a lot!

[@jex4400]

This channel is actually phenomenal it needs to be more popular

[@ComputerScienceLessons]

You are very kind :)KD

[@robf5684]

The clearest and simplest explanation of OOP I've ever seen. Many thanks.

[@ComputerScienceLessons]

Thank you :)KD

[@SosetaFurioasaJr]

I have finally found a concise, 1 line definition of polymorphism. Thank you very much, big thumbs up.

[@rubykanima]

better would be "A subclass can morph / change an inherited method"

[@RVlDER]

Finally a concise and clear explanation about these fundamentals. The amount of interchangeable terms (that still have different meaning(s) under certain context's) is ridiculous - and near impossible to find a video/documentation that explains them without convolution.

[@ComputerScienceLessons]

I'm a great believer in keeping things as simple as possible. Delighted to help. :)KD

[@marktahu2932]

Wow - sometimes the algorithm really does turn up 'gems'. Many many thanks!! As a visual learner this 'gem' is invaluable.

[@ComputerScienceLessons]

You're very kind. Thanks for the comment. :)KD

[@NickHope]

This is excellent. Very clear and precise. I'm going to re-watch it a couple of times to really drive the concepts home.

[@reenalupadhayay4315]

Life saving explanation, better than having to sit through a 2 hour video to understand it. Brilliant!

[@BrainConduit123]

I learned OOP from a video that Philippe Kahn made about the subject when Borland’s Turbo Pascal first introduced this new way of programming. It took awhile to understand and master the concepts, but after that, I absolutely loved it and it made large, complicated projects so much more manageable. The ability to start with a base class and do inheritance was extremely powerful. It literally enabled us to program our products in a fraction of the time and with fewer programmers than the old spaghetti code ways of coding.

[@ComputerScienceLessons]

I agree. It's a great way to manage large projects. I worked for a number of years in software development (albeit as an educator) and OOP allowed hundreds of developers, in different parts of the world, with a range of skills, to work together effectively on very complex applications. :)KD

[@onyemanwokolo441]

I keep coming back to this video. The OOP concepts are well explained in simplest and clearest way.

[@ComputerScienceLessons]

Delighted to help :)KD

[@MisterRose90]

Wow. Someone who could explain inheritance in an intuitive way. It actually makes a lot of sense.

[@brayanrc4432]

The clearest and simplest explanation of OOP. Thanks!

[@ComputerScienceLessons]

You're welcome :)KD

[@achtube85]

This was a very clear and in-depth explanation. Thank you!

[@ComputerScienceLessons]

Thank you. Much appreciated :)KD

[@gianni499]

I'm very very impressed. I'm not a strict Java begineer, but I did need to find videos/resources to understand these OOP concepts better. I had watched already 5-10 sources, but yours is just the most clear. Concise, and clear. Very impressive. Thanks!

[@ComputerScienceLessons]

You are very welcome and thank you :)KD

[@salehhassan6057]

You had a very clear and nice way to describe those concepts. But in my opinion, Polymorphism is much more than just the ability to override a method from a super class. Polymorphism is the ability of an object to take on many forms. Thanks for a great video

[@ComputerScienceLessons]

You welcome. Polymorphism catches a lot of people out - so I wanted to keep it very simple for now. One day I will come up with some other examples which make the point that it does indeed literally mean 'many forms' :)KD

[@doughoffman9463]

Yes. The video leads one to believe that polymorphism is only used in subclasses to override superclass methods. Duck typing (not always available, depends on the language) is the more general and useful case where the same message name can be used in classes that have no common superclass.

[@alm5966]

Always good to get a refresher on what OOP is.

[@alekseevegor5357]

I have spent several weeks trying to understand the professor till I found this 9 min video. Now I feel like I've been to the moon an back.

[@lepidoptera9337]

You haven't been to the moon, yet. If you should ever try OOP in reality you will be disappointed though. It does not do any of the things it promises well. The problem lies in the fact that data dependencies in real world applications have a graph structure (a tree, if you are lucky). OOP is not very good at taking care of that and if you try to use inheritance, in particular, then you will find that you are hard-coding assumptions about that data dependency that may change during the evolution of your project, which will make frequent refactoring necessary. There are better ways of dealing with that problem. Try to learn to think about programs as state machines with as few distinct states as possible. Rather than encapsulating data, control state change. Each state change should be associated with a well defined change of the data. That way your data structures can change freely as the project matures, but the basic flow of the program (as seen by both the user and the programmer) stays the same.

[@ComputerScienceLessons]

I am delighted to help. You will hear a lot of negativity about OOP but please bear in mind that it aims to facilitate collaboration and scalability. :)KD

[@lepidoptera9337]

@@ComputerScienceLessons What are you helping with here by distributing your ignorance about proper software engineering? ;-)

[@darianasedkina6340]

This is a new concept fo me and I've watched about a dozen of videos but should have started with this one. The clarity and simplicity of the explanation are unmatched. Thank you!

[@ComputerScienceLessons]

You are most welcome, and thank you :)KD

[@freepboot412]

Will add to the pile of positive comments here and say this is the most concise, informative, and accessible video on the subject I've seen. great work

[@firepower01]

This is such a good channel for understanding computer science concepts, honestly just the best. Thank you!

[@opethforlife]

One of the few golden channels on KZbin.

[@ComputerScienceLessons]

You're very kind. Thanks :)KD

[@deei5130]

This was a very clear and understandable video. Thanks for that man. This channel needs more attention

[@NorthernStrider]

If you sped up this video, then you are not worthy of the uploaders precious time. Thank you for the top notch explanation

[@ComputerScienceLessons]

Thank you :)KD

[@Amy-f3e]

Wow this is the best explanation Ive seen!!! I have atechnical interview tomorrow and I only know data and sql and not much about OOP in debt. THANK YOU for this great educational content. Today they always jump to Python or the programming name directly, but I miss the real theory and thinking.

[@ComputerScienceLessons]

You are most welcome. I hope it all went well. Good luck :)KD

[@ultraman6950]

Hats off, sir. Thanks a lot for making this well-documented video about OOP.

[@ComputerScienceLessons]

You are very welcome :)KD

[@ivangutowski-smith6514]

Thank you, I have watched this video about 5 times over the last week, every time... I grasp the concept you are talking about a little more, and then understand another smaller detail you mention. I really, really like that whilst explaining, you animate very clear, sensible, logical examples as you go, so I can see what you mean as you are explaining it. I still need to watch it many more times fully, but it is clever, logical, makes sense and is super interesting. Thank you for taking all the time to put this together.. your time a few years ago, has helped nearly half a million people... or if like me.. helped 100k people 5x. ha ha

[@ComputerScienceLessons]

You are very welcome, and thank you :)KD

[@MrDuzen12]

This video needs more views! Great explanation of OOP.

[@ComputerScienceLessons]

Thank you :)KD

[@stupidfrog]

Thank you so much, this was very helpful! My professor and textbook did such a poor job of explaining these basics that I felt like I was falling behind.

[@ComputerScienceLessons]

You are most welcome. Glad to help :)KD

[@cherrynoize]

It's been said, I know, but you're a really great instructor. Hope (for others) that you do this for a living.

[@rehanshoaib1648]

The clearest and simplest explanation of OOP I've ever seen. Many thanks. (2)

[@ComputerScienceLessons]

You're very welcome. Thank you :)KD

[@UTRG-UnderTheRain]

This is one of the best explanations that I have come across as a new learner it's very well explained

[@ComputerScienceLessons]

Thank you :)KD

[@hadiali5249]

very clear, concise , precise and comprehensive video on OOP. thank you for the effort!

[@ComputerScienceLessons]

You are very welcome - and thank you :)KD

[@NormaNsNs]

wow I ve been searching for this video the whole day !!! perfectly explained !

[@STEMdecoded]

excellent, could have never understood it so clearly in 9 minutes.

[@shreyashkumarthakur383]

Best video I have seen till now. Attained full conceptual clarity

[@techwithtee8721]

Closest thing to understand Database management system

[@igwe6547]

Best OOP explanation, simple and straight forward

[@ComputerScienceLessons]

Thank you :)KD

[@Matt-iy2cf]

Wonderfully explained! Have not found a better explanation anywhere online!!!

[@ComputerScienceLessons]

Thank you so much. :)KD

[@patriotir]

This was the best explanation I have ever came across! great job and thanks for the video

[@ComputerScienceLessons]

You are most welcome :)KD

[@cd-stephen]

this has been the best video i have ever seen - great analogies and loved how you included all the different terms used to describe the same thing - new sub

[@ComputerScienceLessons]

Thank you :)KD

[@TexasEngineer]

Thank you for your brilliant explaination. I now know why OOP does not work for my type of programming. I deal with mathematical processes and not objects. Data goes in, formulas are applied, results come out, results are stored or presented. OOP fits database problems. My programming fit the chsos of a spreadsheet.

[@bootcamprag]

Great breakdown/explanation of the OOP concept. OOP is one of my favorite areas in computer science/programming applications. Its not as an intimidating as it sounds. Next: I would love to see a short video on the application of these four OOP constructs in terms of their application; write a simple program that demonstrates each of the four areas. Thanks.

[@phoga6463]

Thank you so much! This gets to the point, easy to understand while not oversimplifying it!

[@ComputerScienceLessons]

You are very welcome :)KD

[@cbbcbb6803]

Great job! Thanks for saying what a class is really. The word template was close to meaningless to me. But saying that a class is "code written by a programmer" is far more precise and meaningful to me.

[@granand]

I have seen many as I keep forgetting it but this stands out. Thank you for the creators and the presenter such a clarity and use of just enough visuals. Esp the take away is synonyms which are used, that trips me, After this hopefully not anymore.

[@ComputerScienceLessons]

You are most welcome. :)KD

[@MrFroggster]

Probably the best and easiest explanation. Thank you.

[@zabinoori49]

The best video explains class and object instance creation in such best way (using graphical representation ).loved that 🤩

[@ComputerScienceLessons]

You are most welcome :)KD

[@getTheSchmack]

Big W. You sir, are brilliant. Just look at how many people are heaping praise and all well-deserved. Thank you!

[@ComputerScienceLessons]

You are very kind. Thank you. :)KD

[@markyap4755]

Thanks so much for a great video ! Helps us to relate and thus makes learning "enjoyable" Learning programming is my current "hobby". Thanks again !

[@ComputerScienceLessons]

You are most welcome :)KD If you enjoy programming - have you seen my video on how to make a GeoGuessr type game? :)KD

[@MichaelChin1994]

5:51 "An Employee is *also* a person" The way this is said with such a straight face, I thought it was a set up for a joke, like: "An Employee is *also* a person, unless they work at a Law-Firm."

[@densmac]

10/10 in explaining OOP concepts.

[@xx03_p19]

Many experienced programmers even the very good ones can't really explain Polymorphism clearly! Thanks :)

[@ComputerScienceLessons]

You are very welcome :)KD

[@MiningForPies]

I once was doing telephone interviews for senior developer positions at SAGE (the accounting software company). I asked the candidate if he could give me an explanation of what polymorphism was and an example of where he’d used it. He accused me of making the term up 🤔. “What the bloody hell is that” or words to that effect. He didn’t get invited to a face to face interview.

[@Jack-xn5do]

Studying for my CISSP and this helped me soo much! Thank you!

[@manishmalhan9768]

Such Brevity and Clarity !!

[@alakhdar100]

This is so clean and simple, yet informative, thank you so much, please keep uploading!

[@TheMagicOwL127]

I'm so glad I found this channel, i was just thinking i should get more into programming in my free time. thanks it was super easy to follow!

[@ComputerScienceLessons]

You are most welcome :)KD

[@AdrianTregoning]

SUCH a good video! Thank you. I wonder why it took me so long to find this channel.

[@ComputerScienceLessons]

Thank you so much :)KD

[@maycodes]

What an amazing crystal clear explanation, got confused in university

[@ComputerScienceLessons]

Thank so much you :)KD

[@Wida85]

Surprisingly clear and succinct, thanks for clearing this up 🤝. Please do keep up the good work 🙂.

[@ComputerScienceLessons]

You are most welcome and thank you :)KD

[@nevillecreativitymentor]

I picked a book on OOP 25 odd years back ... TODAY i understood the fundamentals LOL LOL ... thanks for the video ♥♥

[@ComputerScienceLessons]

Delegated to help, albeit a little late. You are most welcome. :)KD

[@dr.SaurabhSingh.D]

The clarity at its peak. 👌

[@justincatterall9597]

*Now* I understand polymorphism. Thank you!

[@ComputerScienceLessons]

You're welcome :)KD

[@Zeila1]

i wish i watched this at the start of my OOP subject, the way you explained it made it so much easier to understand, the examples you used and visual effects really helped also. edit: I also remember watching your Dijkstra's Shortest path video back in highschool, that was also amazing.

[@ComputerScienceLessons]

That's great to here. Thanks for commenting. :)KD

[@michaelcappello2254]

Very clear explanation of the basics of OOP. Thank you.

[@ComputerScienceLessons]

Thank you :)KD

[@marcuss8454]

And just like that, I subscribed to this channel for such a great explanation.

[@michellemwangi3963]

The entire series is really really good! very well explained. Thanks a lot

[@lucasbozdog5922]

this is one of the best explanations i have seen thank you

[@kopilkaiser8991]

Thank you for your explaination. I've learnt quite a lot from watching your video. Keep up the good work in teaching beginners like me.

[@ComputerScienceLessons]

Thank you :)KD

[@velocitydelta]

This is a great video! My teacher shared it with us to revise the concepts we are learning currently in school!

[@ComputerScienceLessons]

Thank you so much. I'll be on the curriculum next. :)KD

[@TonyTigerTonyTiger]

The part on inheritance has some potential theoretical issues, but it is after all just an introduction. Generally speaking, inheritance should be used to model "is a special kind of" relationship, and should not be used to model as "is a role played by a" relationship. An employee is not a special type of person, it is a role played by a person. Same goes for Customer: that is not a special type of person, it is a role played by a person. For example, Alice could be an Employee of Walmart, but she could also shop there so could also be a Customer of Walmart. So if you are creating an object for Alice, would you create an instance of Employee or Customer? On the other hand, a dog "is a special kind of" animal, not a role played by an animal; and a fish "is a special kind of animal", not a role played by an animal. A dog cannot simultaneously be a fish, nor can a dog quit being a dog and become a fish; and a fish cannot simultaneously be a dog, nor can a fish quite being a fish and become a dog. So here inheritance does not suffer from the above problem. If you have a pet dog named Wolfy or Max, there is no ambiguity in what class you would use to create an instance for your pet: it would be a dog.

[@ComputerScienceLessons]

I see what you mean. However, the context of the system you are designing is important. If for example I was building a payroll system, and Alice was an employee, it is probably neither here nor there if she is also a customer (staff discounts excepted). :)KD

[@arahn466]

"So if you are creating an object for Alice, would you create an instance of Employee or Customer?". what is the answer? u shouldn't create 2 instances should u?

[@sargata3054]

This is such a clear and concise explanation. Thank you from a beginner dabbler in programming!

[@andregrobler4393]

Very concise and accurate. Most helpful, thanks.

[@AndrewSinclair]

Thanks.This is the best OO explanation ever.

[@ComputerScienceLessons]

You're very welcome. And thank you so much :)KD

[@masterrov1030]

Thank you for teaching these basic pillars of OOP

[@ComputerScienceLessons]

You are most welcome :)KD

[@ujjwalsingh8975]

had so many doubts after my OOP class this cleared it all

[@ComputerScienceLessons]

Delighted to help. :)KD

[@xdebono7613]

Brilliant….. concise and awesome clarity….thank you

[@ComputerScienceLessons]

Thank you. You are are most welcome :)KD

[@shivohamjagat]

One of the coolest videos I have ever watched

[@showaibhaydar9590]

This is a super clear way of defining and demonstrating the concepts ! infinite Thanks ❤‍🔥

[@ComputerScienceLessons]

You are very welcome :)KD

[@a-60harshalmaheshram30]

This video cleared my most of the doubt , very great and deep explanation.

[@emmamorris1092]

massively useful definitions of OOP terminology - thanks!

[@ComputerScienceLessons]

You're very welcome :)KD

[@itorres008]

Amazingly succinct, clear and thorough!

[@lepidoptera9337]

Yes, that was the academic's view on classes. What the academic doesn't tell you is what it means in practice. For one thing, your compiler removes any and all the class code and turns it into plain old subroutine calls anyway. This means that your classes are mostly documentation. They are not necessary and all of your hundreds or thousands of hours of work goes "poof" in a few seconds during one of the compiler passes. The second thing classes are, and this is way worse, are leashes. The architect is basically telling you through classes what you, the application programmer, can and can not do with the data that you are given. You start out with a Turing complete language and by reducing your data access through class methods the architect limits your work to something that is anything but complete. Ideally they want you to be helpless and caged in in the narrowest possible way. Why is that? Because they don't trust your creativity as a programmer. Creative problem solving is considered "error prone". What class hierarchies allow the architect to do is to say "The guy in cubicle one can only paint in red, the girl in cubicle 15 is only allowed to use two shades of green!". Is that the kind of job you want for the rest of your life? Or do you imagine that you will be happy as an architect who gets paid to put computational leashes on people? Is that the life you are dreaming of? And now the worst part... if the leashes are wrong, then everybody gets caught in them all the time. That's when the great refactoring starts. Refactoring... that means breaking a working system for the simple reason that the program documentation was wrong because the architect messed up during the first three weeks of the product development (which was eight years ago and done by a person who has long left the company...). :-) That is the actual reality of object oriented programming.

[@taniatech_official]

Simple and straight forward. Thanks a lot!

[@ComputerScienceLessons]

You're welcome, and thank you :)KD

[@tuck295q]

This video is mad with super clear and simplistic yet uber effective explaination. xD

[@ComputerScienceLessons]

Thank you :)KD

[@CenturionVII]

Really upping the animation quality, very nice sir!

[@ComputerScienceLessons]

Thanks for noticing. I was playing around with a very old version of Adobe Flash :)KD

[@dimlavalentine3263]

You are really a lecture with a unit voice. love this unlike your lectures on floating points

[@larsAnder]

I like the interface you just briefly mentioned, you just don't know how much that clued me in.😁

[@johnjacobjinglehimerschmid3555]

Why this one's understandable I'm not sure. But over the many years of listening to vlogs on OOP .... this one seems to make the most ( simple ) understanding for me.

[@ComputerScienceLessons]

As a teacher, that's music to my ears. :)KD

[@brandonwilcox3307]

Clear, concise, and informative. Thanks!

[@bryanpepe2395]

Amazing explanation. Good job!

[@ComputerScienceLessons]

Thank you :)KD

[@exoticme4760]

This was a very very very good video. Thank you so much ! I hope my interview goes well :)

[@ComputerScienceLessons]

You are very welcome. Best of luck. :)KD

[@exoticme4760]

@@ComputerScienceLessons thank you 💗

[@TreyHope]

Very solid explanation, perfect breakdown. Thank you for sharing.

[@ComputerScienceLessons]

You are very welcome. Thank you :)KD