OOP interview questions :- What is the difference between Abstraction and Encapsulation ?

Very nice...

Good Example. Thanks

Best i ever heard.. 😂

AMAZING VIDEO! I was worried that this video wasnt what I was looking for, but damn was I wrong. Thank you!

Amazing thank a lot ❤️

Clear and simple, Thank You

I am regularly watching your videos to get theoretical and practical knowledge on C#. I would say I'm a junior developer coding for years but recently from mid of 2022, I took C# seriously. Your videos are helping me to elevate my understanding much higher, and being able to understand in depth. Thank you for your hard work. I will keep watching, share with others, and share my thoughts on each video unless I'm feeling lazy to comment.

nice explanation

This one helped a lot a lot🤧

2022 and this is still the best explanation

next level explanation

Great vid!

Better than my 3000 USD uni course

Sir you have made this so clear. Thank you

Very nicely explained , thank you sir

You Perfectly clarify my confusion🌼

So abstraction is a concept to simplify the data what the end user need.
And encapsulation is to encapsulate the complexity methods that we don't want user to know.
(Encapsulation implements abstraction)

Great video. Thank you

Myth broken, thank you for making our life easier.

浓浓的咖喱味儿

I understand the objective of the video is different and it's just a sample code, but having CreateDBObjects() in Customer is not optimal design.

Great vídeo, congratulations

Thank you so much, today i unserstood finally the difference

Great explanation 😀

You have helped me clear this concept 🤗

One word... Excellent!!

Awesome Sir I learned very clearly what exact abstract and encapsulation

very good explanation

Thanks a lot

❤❤

Thanks for this it helped

Watching in 2021

You didn't run the code?Amazing time wastage

Thank you sir

You freed me of confusions! Great job

what an explanation!! best ever..Shiv Sir is always the best

nice!

That explanation was really good. Absolutely no confusion!
Thank you very much!

Very well explained man

Thank you so much, Sir. It gives a clear understanding

The last four minutes of the video, was what chnaged my mind. I loved the way you tabled it. Mean explanation. Thank you very much.

Best explanation 😊

Simple and clear.. thanks for video

Brilliant explanation, thanks so much 🙌

very nice explained .

For beginners : Having your DB access code inside your POCO isn't a good idea as it violates SRP (Single Responsibility Principle). In short, your Customer class should never call upon DB from within. Also, you should never instantiate objects in your main code. Object creations, deletions etc.. must be "deferred" to a different handler, a "Factory" method which will create and return the required objects.

Now way better to understand. Thanks for the video.

very well explained Sir