Is it good to use events more often?

$$anonymous$$anaging growth and complexity are very deep, abstract topics. There's no prescribed approach which guarantees the "best" experience for the developer. Learning about and leveraging the strongest principles from various design strategies is the right answer to this question. Using delegates and events is a strong feature when it's appropriate, but does imply some overhead. Balancing your design strategy between convenience, performance, and sense is a career-long discovery. As your experience grows, you'll become familiar with the tools at your disposal and the strengths and weaknesses thereof. Apart from general program$$anonymous$$g "best practices", the wisest approach to a given requirement will always vary case-by-case.

So the other answer to your events question is the same answer to give anyone who asks about a specific feature: Choose the strongest feature or design archetype you can based on experience and foresight. When facing similar situations, use a similar solution. Before long, the strongest (or your favorite) approaches to various situations will become obvious to you. I think everybody learns this stuff the hard way. ;)

Thanks AlwaysSunny you helped me to sort out some confusion. It really helped and thanks again for your time. :)