I was playing the kudvenkat Sir Video's at 1.25 speed and have found myself playing Avish Sir video's at the same speed :). By the way the content is great and is one of the best explanation available on the internet about implementing design pattern using C#
happy to see you back. Just a request can you please make a 2-3 videos together or at least complete 1 design with one go because time between two videos are much more so it's hard to remind all the things and have to watch all the videos from start to end. Nothing other than this. It's awesome to see real time example. thank you for this.
Nice video. One suggestion: Better if you can explain the concept/blueprint in simple words at the starting than giving heavy definitions. The concept,problem and how it solves like we explain on paper. Jumping to implementation needs lot of time to understand what is achieved. Thanks again for the video.
Suggestion: Wouldn't it be nice to describe scenario what we are going to implement before jumping to code? Kind of blueprint at high level.. Content is good but couldn't related to why we are doing this . Thanks for making this video. Appreciated !!!
Nice video and got a good idea about FMDP.. I have one quick question, Why we should not put this all this computational or business logic in a simple stored procedure rather than following this pretty pattern just for applying some regional rules. Does it make sense, because it will give more flexibility and you can change rules when ever you need. Because at the end you just need to store Employee object and you can do it easily with SP by applying what ever rules you need.
Summary - through this approach, we are basically creating three heirechy factories. One for common class operations, one for specific to the class and last for interacting with the client for giving final result object. Am i right ?
Very nice and clean explanation Avish. But one doubt let say if i want to call specific functions/methods for permanent/contract employee from controller then how can i do it. Let say i want to add new employee which i want to expose as API then how to do it. do i have created a object of permanentemplyee class ?
Hi it was awesome and easy to understand for a beginner like me.... I had a doubt though..... The applySalary() method has a return type of Employee object but is is not being stored in a variable.....so can that be a void function....if not why?
Nice explanation and methods, thanks a lot, but there are lot of codes involved on the front end. I would prefer to do all these on the back-end i.e. database stores procedure etc.
I think the ApplySalary() method should not be creating the base employee factory instance. Am I wrong here? The way it was coded it seems to be adding a hidden behavior. Shouldn't ApplySalary() be only about applying salaries? My intuition says it should receive an employee instance and return a void. I guess that means that depending on what the lazy or immediate requirements are, the factory would expose an additional method for loading. Thoughts?
Thanks for the tutorials..Realy good tutorials...But I did not see the concepts releated to OOPS Encapuslation,Abstraction....Please post those tutorials also
I think you have provided the wrong example for this. you should show the example where you can get the HRA or MRA to the controller based on object type ultimately the client should be only aware of the creator(Base Employee Factory) and the Product(IEmployeeManager) in your case. Actually to satisfy the factory Method implementation you may need to introduce 2 new concrete products. Correct me If I'm wrong
On 12.20 you have created ApplySalary() method whose return type is Employee. 1) I think the method ApplySalary() should have void return type. 2) What is the point of returning Employee object from ApplySalary() method? As it is the same Employee object which you are passing from controller. So in controller we already have Employee object so returning same Employee object from ApplySalary method doesn't make sense here. Please suggest.
Very complicated example. Could take a logger example or dbcontext or dbconnection where subclass pass a parameter to factory and factory further call the concerete class for final result object. Your example is almost similar to my examples.
Thanks, but it could be better to have more experience development with a simple example and why we need to use those abstract classes and why we need to use one pattern instead simple implementation. What is the really benefit of that!
Question : When we created House Allowance etc and you said : if we change the EmployeeManagerFactory to accommodate the changes, It will voilate the principles of Creation Factory Patterns, Exactly which principles were in danager/violation ? Regards, A Learner.
If we don't use factory method, then the simple factory would have to do specific creation code like medical allowance in the switch case statement - which violates the principles of encapsulation - with factory method, that creation code goes to the class where it belongs.
I don't think this is ok , to have side effects in your Create() method of your factory. When i call Create() method , i never expect for it to also set medical or house allowance for employee.
Sir you are too verbose. You don't have to repeat yourself whenever you are using the new keyword for object creation or creating the constructor or bringing the using reference... It is little irritating and difficult to focus things in our mind thus making simple things unnecessarily complicated. However overall it is an excellent video.
I am taking my skillset to the next level after going through these really awesome videos. Thanks a lot.
Such a great lesson Avish. The quality of your narration & program representation is excellent.
I was playing the kudvenkat Sir Video's at 1.25 speed and have found myself playing Avish Sir video's at the same speed :). By the way the content is great and is one of the best explanation available on the internet about implementing design pattern using C#
Tahnk you so much for wanderful lessons, very clear explaining with code example.
happy to see you back. Just a request can you please make a 2-3 videos together or at least complete 1 design with one go because time between two videos are much more so it's hard to remind all the things and have to watch all the videos from start to end. Nothing other than this. It's awesome to see real time example. thank you for this.
Nice video.
One suggestion: Better if you can explain the concept/blueprint in simple words at the starting than giving heavy definitions. The concept,problem and how it solves like we explain on paper. Jumping to implementation needs lot of time to understand what is achieved.
Thanks again for the video.
Suggestion:
Wouldn't it be nice to describe scenario what we are going to implement before jumping to code? Kind of blueprint at high level..
Content is good but couldn't related to why we are doing this .
Thanks for making this video. Appreciated !!!
🙏 Good explanation Avish. Keep going, I'm learning lot of new things. Now I'm confident an Factory.
Nice video and got a good idea about FMDP.. I have one quick question, Why we should not put this all this computational or business logic in a simple stored procedure rather than following this pretty pattern just for applying some regional rules. Does it make sense, because it will give more flexibility and you can change rules when ever you need. Because at the end you just need to store Employee object and you can do it easily with SP by applying what ever rules you need.
Oh well... Now this one is a little bit trickier than the singleton and the simple factory man.. Anyways lets dive deep.. Nice tutorial.. Thanks..
V nice explanation.. thanks for sharing knowledge...
Summary - through this approach, we are basically creating three heirechy factories. One for common class operations, one for specific to the class and last for interacting with the client for giving final result object. Am i right ?
Thank you so much Avish for your wonderful lessons!
Now I do not fear from factory pattern .. thanks :)
excellent real world based example.. thank you...keep the great work
I liked your explanation. Thank you, Inside factory why do write business logic in 'BaseEmployeeFactory' other than creation of object
Very nice and clean explanation Avish. But one doubt let say if i want to call specific functions/methods for permanent/contract employee from controller then how can i do it. Let say i want to add new employee which i want to expose as API then how to do it. do i have created a object of permanentemplyee class ?
i think you will have to Convert it to the concrete class , for you to be able to do it.
Hi it was awesome and easy to understand for a beginner like me.... I had a doubt though..... The applySalary() method has a return type of Employee object but is is not being stored in a variable.....so can that be a void function....if not why?
Nice explanation and methods, thanks a lot, but there are lot of codes involved on the front end. I would prefer to do all these on the back-end i.e. database stores procedure etc.
I think the ApplySalary() method should not be creating the base employee factory instance. Am I wrong here? The way it was coded it seems to be adding a hidden behavior. Shouldn't ApplySalary() be only about applying salaries? My intuition says it should receive an employee instance and return a void. I guess that means that depending on what the lazy or immediate requirements are, the factory would expose an additional method for loading. Thoughts?
Im new to this, but I have often seen loader methods being used with factory method designs, so I think you are right.
Thanks for the tutorials..Realy good tutorials...But I did not see the concepts releated to OOPS Encapuslation,Abstraction....Please post those tutorials also
It looks like inception movie😁 but overall nice explanations
😅😅
Very good webcast/video. Console Application as a lathe machine would be better for understanding web/desktop/UI developers;
I think you have provided the wrong example for this.
you should show the example where you can get the HRA or MRA to the controller based on object type
ultimately the client should be only aware of the creator(Base Employee Factory) and the Product(IEmployeeManager) in your case. Actually to satisfy the factory Method implementation you may need to introduce 2 new concrete products.
Correct me If I'm wrong
Team,
Some tutorial uses abstract class and some tutorial uses interface, which one is the correct choice? and why ?
Where is Venkat - we request him to teach this
Great team, appreciate your effort.
On 12.20 you have created ApplySalary() method whose return type is Employee.
1) I think the method ApplySalary() should have void return type.
2) What is the point of returning Employee object from ApplySalary() method? As it is the same Employee object which you are passing from controller. So in controller we already have Employee object so returning same Employee object from ApplySalary method doesn't make sense here.
Please suggest.
I agree with you, i think there is no need to make ApplySalary() return _emp
and after returning it where did he you it again ?
Very complicated example. Could take a logger example or dbcontext or dbconnection where subclass pass a parameter to factory and factory further call the concerete class for final result object. Your example is almost similar to my examples.
Thanks, but it could be better to have more experience development with a simple example and why we need to use those abstract classes and why we need to use one pattern instead simple implementation. What is the really benefit of that!
Exactly
Thanks. Can you plz train us on how to design a Framework...form Technical Architect Prospective...
Can someone explain to me how does the this.Create() work? What is "this" referring to when we call the ApplySalary?
Question : When we created House Allowance etc and you said : if we change the EmployeeManagerFactory to accommodate the changes, It will voilate the principles of Creation Factory Patterns, Exactly which principles were in danager/violation ?
Regards,
A Learner.
If we don't use factory method, then the simple factory would have to do specific creation code like medical allowance in the switch case statement - which violates the principles of encapsulation - with factory method, that creation code goes to the class where it belongs.
at 15:10 how is the employee object created from the data entered in the form ?
hi is Factory DesignPattern replaced by Dependency injection. If not then can we implement both in one project
Thanks for osum explanation.
Very well explained. Thanks a ton
thanks, Avish for the video can you please attach the zip file of the source project along with the video
Such a great lesson
Thank you, Avish :D
its look complex to me.... :(
simple, easy, effective
Thank you Arnab. Very glad you are finding our courses useful.
Pleae provide more example to get more claity
Thanks a Billions.
I don't think this is ok , to have side effects in your Create() method of your factory. When i call Create() method , i never expect for it to also set medical or house allowance for employee.
amazing keep it up sir
Sir you are too verbose. You don't have to repeat yourself whenever you are using the new keyword for object creation or creating the constructor or bringing the using reference... It is little irritating and difficult to focus things in our mind thus making simple things unnecessarily complicated.
However overall it is an excellent video.
We can write triggers to achieve this. Also it was too complicated to understand.
It would be helpful if you keep your example very easy.
It was a bit complicated and lot of hierarchies involved, and also didnt understand the this.create.
15:40 shouldn't db.Employees.Add(employee); will become db.Employees.Add(empFactory): ???
sathyama purila