2 cents: in the most compact form of an observer pattern you don't need a subject parameter in Update(). You only need it if you do something based on the subject like the _celsius_ temperature. Or if there are multiple subjects. Nice explanation BTW!
Something seems off, in NewsAgency -> Update method after casting to WeatherStation I have access to Notify method, I should not have so that I don't call it explicitly
observer can update the temp through the object you send to him ,and that will crash the program, due to continue calling the notify each time and then we set ,notify ,,, (stack overflow)
Thank you, this will get me a better grade at my test tomorrow! Feedback: The explanation throughout the video was very good - at the beginning however, the part with the interfaces was lacking details.
So in 15 minutes I got exactly what I needed to fully understand the observable pattern in C#. Subscribed immediately!
Agree, no need to hunt more..
Excellent.. Excellent... Excellent. I love you man. I now got Observer Pattern
2 cents: in the most compact form of an observer pattern you don't need a subject parameter in Update(). You only need it if you do something based on the subject like the _celsius_ temperature. Or if there are multiple subjects.
Nice explanation BTW!
I subscribed right after watching the video. Was really helpful.
Awesome tutorial! Clear and concise. Thanks much!
Thanks for the quick and clear explanation!
String interpolation would be nicer, good video though. I would probably use pub sub through redis
Beautiful explanation... Thank You.
It is very clear explanation. Thanks.
You are welcome!
Very nice explanation... Kudos
Nice explanation. Thanks for your quick demo..
You are welcome!
Something seems off, in NewsAgency -> Update method after casting to WeatherStation I have access to Notify method, I should not have so that I don't call it explicitly
Very nice explanation. thank you
observer can update the temp through the object you send to him ,and that will crash the program, due to continue calling the notify each time and then we set ,notify ,,, (stack overflow)
Isn't it better to inject ISubject via constructor in observer?
What's the difference between creating all of this observer pattern code vs just using events and subscribing to those events?
It's just to show you how it all works but ofcourse you can do your custom implementation as well.
Perfectly simple and very clear explanation.
Thx.
(I subscribe to your channel )
Should we really pass the subject with a public Notify() and expose that method to every observer?
Excellent video
Thank youu!!! I understand it perfectly :)
Simple and easy 👍👌
Alguien me puede decir donde encontrar el codigo?
very presice and clear, this is the exact explanation i was looking for!
Can u post a good tutorial for osberver in C# ?
easy nd crisp
Thank you, this will get me a better grade at my test tomorrow!
Feedback: The explanation throughout the video was very good - at the beginning however, the part with the interfaces was lacking details.
Thanks for the review! All the best for your test.
Nicley explain
good Job :-)
weather estation
its not ikual tu null.
The code is not your repo
Maybe talk more clearly and slowly