Couple of correction for the viewers of this video from my point of view, - Clean code book has no dedicated topic or chapter for SOLID. - Uncle Bob[Robert Martin]'s other two books Agile Software development PPP and Clear architecture are talking on this topic in detail. - SRP can be viewed from different level like Functions and Classes, Component and architecture. At each level same principle is sharing some insight. This video is presenting one view of it however, it doesn't mean that There should be a single reason to change a class is incorrect and that's not what SRP is. People who are confused can Read SRP principle from both the books that I mentioned above. By heart I am appreciating author's good quality work and commitment to sharing with community however, above points are extension and slight correct to guide users on further reading.

@Dino-yw1td

Жыл бұрын

In fact, in the Agile Software Development PPP book, at the beginning of the SRP chapter, it explicitly states "A class should have only one reason for change."

Loving this LLD series. Patiently waiting for the Open/closed principle! 🙏🏽

This is an AMAZING explanation. I have been looking for a really good explanation of the single responsibility principal for years to truly understand it, and this takes the cake!

You are a gem. Thanks for explaining it in the best possible way while breaking the myth. Appreciate your efforts. It helps a lot in preparing the LLD preparation.

I understood SRP clearly for the first time. What an amazing explanation! Your examples are really good too, thanks for giving two examples with slightly different perspectives

Yogita, you're just amazing! Thank you for bringing such content to us. The way you explain so much in a limited amount of time is commendable.

The best graphics, I've seen in any video so far! Literally graphics are one of the USP of this series. Thanks for putting such great quality content!

I am addicted to your way of teaching.It gives me more and simple ways of learning topics.Thank you.

You are the smartest person I have ever seen explaining Low-Level Design. Thank you very very very much 😍😍♥♥♥♥

Yogita, your videos are well researched, well narrated and well presented! I feel so much comfortable watching videos, because I can trust whatever you're saying.

Good job! So many people get this wrong, especially other content creators. Thank you for helping debunk the dogma around S.R.P. 🎉

Yogita thank you so much for bringing such a great content. I’m an aspiring technical architect this will surely help me.

awesome explanation.. there is no other video which explains this principle so clearly...

Great video and breakdown of SRP. I don't know who out there thinks one public method on a class is a good practice, but they definitely have their wires crossed.

Thank you for the quality content.Please make more videos in the LLD series.

The best explanation on this topic on youtube

Such a great explanation of this concept. Thank you!

amazing graphics, very nicely explained and a very well delivered video, thanks for your hardwork, I got to learn something useful today

Thanks Yogita. I can learn very well.

Thanks for this, it really helps me as a student hehe can't wait to watch the Open/closed principle :)

amazing. waiting for next vids in course

Hey excellent teaching love you please don't stop uploading

Can't wait to see your next video

Top notch explanation, thank you very much!

Great explaination! Thanks for such amazing content!

Great explanation. Thank you

Amazing explaination! Learning a lot here

Hi yogita, can you pls upload videos more frequently so that i can stick to your playlist.. ideally if you can upload 3+ videos per week it would be really great for prepping for interview.

Ma'am, please, also explain the other parts of SOLID principle. Really, awesome 😊

Thanks a lot ma'am for explaining in easiest way

Seriously , great explanation

Great Content. thanks yogita

Thanks yogita for amazing content, would it also be possible for you to make a video on open closed principle. Rest all the solid principles are covered really well in great detail

Honest efforts in making these videos. Very helpful !!

@sudocode

2 жыл бұрын

Glad you like them!

Finally I found a best vdo in KZread ❤️

Superb explanation !!!

amazing logical explanation

very very helpful for me for learning LLD

Good explanation ❤....

Thanks for the great content!

Awesome explanation.

Videos in this series are very good . If it is possible could you please upload more content

crystal clear explanation

Thanks, Yogita excellent explanation, but I can't see the video for the Open-closed principle in the playlist.

appreciate your work.

Very good explanation 🤩

The explanation was crystal clear, especially for the Hotel example. if isPaid is added with the getter and setter method instead of constructer, how would that break?

thanks for nice tutorial , but what happen for the "getRegularHours()" method in first example after separation classes? how can fix share code in two class ? duplicate code or using interfaces?

Thanks for this video

Then in this case one class can have mostly one pulblic method when it comes to real time implementation. Can't argue with your explaination, very clear....

Great 👍

Super content! Please increase the upload frequency Yogita! :(

Can you give an example where srp is followed and the class has more than one method. Thanks. Loved the video :)

Hey, Could you please explain how in the first example decomposition to different class would help us if for CFO we need to make changes in common getWorkingHours method? Also in 2nd example if we need to add more fields in db, even if we create new store class, we would still need to pass isPaid from bill class to store it. Eagerly waiting for your response for clarification on these. Thank you

Does the additional method of subclass violate the LSP which is not present in the parent class?

A small doubt, if we separate also, still CalHours need to used by CalSalary need to know regularHours(), so where do we need to place this ? If it write in two classes are we not violating DRY ? Please comment

Awesome... Lucid ...

Brilliant !

Amazing Superb explanation. thanks from my heart :) Happy teacher's day guru ...🙏

@sudocode

Жыл бұрын

Thank you so much for the wish. At least I got one wish on teachers day. I will keep it. Thanks again.

Yogita. you are amazing on the explanation. Do we have 2nd design principle Open Close?

Informative video and nice animation...keep posting 😊

@sudocode

2 жыл бұрын

Thanks Anek

Could you make video for second principle of solid ie. o - open/closed principle?

Hi @sudocode, Thanks for the explanation, but one doubt here by seeing the explanation - how a developer will know beforehand that who the different stakeholders can modify the code?? For ex in a class having different methods, how will a developer know while designing that needs to segregate the methods to different classes based on stakeholders beforehand?

But if both calculateSalary and calculateHours methods use the same getRegularHours (maybe it will be a little different for each type), but if you separate it, will the code be duplicated? And although the editing is independent, if additional operations are needed, do we have to edit it in 2 places instead of editing it in 1 place?

Now when i give this ans to interviewer. Hoping he would have read uncle Bob too or have seen your explanation😊

But won't it mean that if I create separate class for both calculateSal and calculateHours, then I'll have to copy paste the same logic for getRegularHours and there's code repetition?

Congratulations mam u got a new subscriber it's me 😁

Hi . It's very helpful courses for OOP ,OOD and more, thanks for your efforts

@sudocode

2 жыл бұрын

👍🙂

@prashantrajawat2829

Жыл бұрын

@@sudocodeMam please complete remaining video of solid principles. Your explanation is amazing 👍

Waiting for more videos didi 😄

Oh, I was looking for something else, and saw your thumbnail! You look so like *NAIROBI* from _La Casa de Papel_ :)

@sudocode

Жыл бұрын

Hahaha thanks. I get that a lot.

Thats the idea behind common closure principle (CCP) & Applying DDD (Domian Driven Design) - The basic idea behind microservices

@sudocode

2 жыл бұрын

Yes!

Amazing 😍

@sudocode

Жыл бұрын

Thank you! Cheers!

This is true layman terms from coding perspective that everyone seeks. Thanks for not following the traditional bookish knowledge.

I am bca first semester student,after I will also do MCA than Can I eligible for FANG company.

Thank u

Mam, where is the open close principle? You lecture 106 is not open close principle.I dont want to move to L without knowing O. If anybody has the title,please let me know

Thanks Yogita for sharing such useful content !! You are an inspiration... I sometimes get confused while breaking the classes and end with lot many classes like models(with mainly properties and getters setters), service classes (service class for model classes to perform certain tasks like play, save, move, etc) and repositories (for saving objects in memory). Could you help me understand if this approach is correct or not? Is it fine to have separate service classes for having the business logic instead of putting a lot in model classes. If yes, should I create it as a singleton class, class with static methods or like a normal class, because it will be mostly performing business logic without maintaining any state.

@rajaganji7982

2 жыл бұрын

It is okay to break classes into multiple model classes. If there are N entities (credit card, user, cart,classes etc..) you can create different model for each of these like (credit card model, user model...ETC). You can use get;set methods to wisely encapsulate the porperties of the model class also. If you look at MVC architecture. This is how it is done. Model classes hold data and service classes are used to apply bussiness logic on top of these models. Making all the methods static and using singleton is not a good idea. As you practice solving LLD problems and multiple design patterns you will understand the beauty of OOP. If your not using OOPS to max ability then your just using Functional programming with model classes.

So, can we make it a thumb rule that - If there are more than one actors for a method then just make it a class?

Thank you❤

@sudocode

2 жыл бұрын

Thanks backlogbatch 😇

Where's Open Closed principle? It's not existing in your list

Hey mam wonderful explanation mam thank you so much mam 🤗🤗🤗................................................ :-)

Hi Yogita, First, You are doing great job and I am learning something new in the end after watching every video of yours. Keep up the work! Second, I have doubt in the both the examples. Even though we decomposed the methods to different classes, still impact is there when change happens. For example, getCalculateHours is still needed for both CFO and HR. where this method will sit? and when change is required, still both classes have impact, right? In another example , if Bill Store class required new param like isPaid, anyway that should be sent by Bill class as that new param is relevant to Bill object. Again, change is needed on Bill class. Please correct if my understanding is wrong.

@salwenikhil456496

Жыл бұрын

Same question im having if you got the answer plz comment.

@SakshiSingh-arcane05

Жыл бұрын

method getCalculateHours would reside on both classes, would be private to those particular class, hence any change done for getCalculateHours of calculateHours wont affect implementations in calculateSalary.

Understood

Wow.

I thought I'd seen the most beautiful programmer but I was wrong.

Does applying object oriented design to real world models come with experience?, thanks a lot for replying.

@righvedkumar2159

2 жыл бұрын

I would highly appreciate your reply

@sudocode

2 жыл бұрын

Not completely through that. It's more like you should have an understanding of oops concepts well. And then of course, the more you practice, the better you would get at it.

@righvedkumar2159

2 жыл бұрын

@@sudocode thanks a lot! I love watching your content!

Why more video are not comming now days and this particular series of lld

@sudocode

2 жыл бұрын

Will come soon.

ma'am please make more videos

When are you uploading open close principle?

@sudocode

2 жыл бұрын

It will take some time.

When you will cover design patterns?

@sudocode

2 жыл бұрын

After solid principles

@hemantsah8567

2 жыл бұрын

@@sudocode will be waiting for that,

I'm literally falling in love with you

I m in love with u maam😍

Please share the contents in slow way. Most of the things will go to out of our mind

@sudocode

2 жыл бұрын

I am really sorry for the speed. Please bear with few more videos as those are record. Will make sure doesn’t happen in new ones.

@akashkeshari5436

Жыл бұрын

Yes, that is one of the problems with the videos like too much content in a single sentence. Despite this, the content is good and the teaching is also good.

Hi Yogita, I am loving the content you are posting on KZread. In one of your Low level design videos (kzread.info/dash/bejne/eJaFu8ufp5yolZs.html) , you mentioned Obect oriented design is hard, what do you mean by that, does it mean it is really hard to grasp low level design, could you clarify that. Your response will be highly appreciated!

@sudocode

2 жыл бұрын

I appreciate your persuasion skills but you have exhausted every possible way of communication to get answer for this question. Yes it is hard to convert real world models to object oriented design due to its subjectivity and the requirements in place. It’s not hard to grasp, it’s hard to apply. Please try to be patient while asking questions. Attention seeking never helped anyone progress.

@righvedkumar2159

2 жыл бұрын

@@sudocode thanks a lot and I understand, I wont bug a lot in future

@righvedkumar2159

2 жыл бұрын

@@sudocode just one last question,Does applying object oriented design to real world models come with experience?, thanks a lot for replying.

You are not actually teaching for interviews it seems - I mean, that could be a side effect, but not the target. what I have seen in KZread is things been spit out and asked to be remembered. This is far from it.

Aap ko hindi nahi aati

@sudocode

2 жыл бұрын

Aati hai. Aur aapko english?

@abidkhan.10

2 жыл бұрын

@@sudocode yes mujhe english nahi aati aap hindi english mix kro please