C# Delegates and Events | Theory vs Real interview answer

Good morning, good afternoon, good

evening from whichever location you are

watching this video. A very very warm

welcome to Quespon channel and in this

video we'll be discussing about what

happens in actual interviews when it

comes to delegates and events right and

the whole goal of creating this video is

that

to make you understand that when you

talk about interview preparation when

you talk about clearing interviews right

it is not just a technical thing

technical thing must be 70% but 30% it

is psychological 30% person it depends

on that what kind of answers you are

giving to the interviewer and what kind

of cross questions the interviewer asks

you right so what this is what this

video is all about and again before I

start this video if you go and if you

share this video on your LinkedIn you

will get this beautiful shear interview

question PDF right so go ahead share the

link and mail us at questpondqubond.com

and we will give you this beautiful book

out there so let us get started when

this question comes up in the interview

Many developers answer that delegate is

a pointer to a function. Now this answer

is actually technically very right but

it is very very academic. The next cross

question that the interviewer can hit

you is with that why do I have to call

the method through a pointer? Why do I

have to invoke the method through a

pointer? I can invoke it directly and

this way what will happen is the

interviewer will will go in a different

tangent altogether. So it is better to

answer some practical implementation out

here right that's what impresses the

interviewer if you're going to go around

with your academic answers right the

interviewer will never connect with you

so for example if you say here delegate

is a call back so for example you have a

caller and you have a colleague and let

us say that the caller and the colleague

are in a different process in a

different thread um you know and they

want to have communication between them

then must be it makes sense Right? So

when you start with the right answer,

when you start with a practical answer,

the interviewer starts connecting with

you. So answering academic answers,

right, just makes the interview very

mundane. Uh another kind of answer which

comes around delegates is that delegates

are like abstraction. Now remember when

it comes to abstraction, right,

interfaces are gods of abstraction

frankly. So

when you actually put ahead this answer

saying that delegate is like abstract

over any kind of a method like for

example you have an method which is

operation it takes two number now inside

that it can do an addition or it can do

a multiplication or it can do something

like that. So when you say that delegate

is an abstraction over a method

signature, the interface can take you

into a different loop and ask you that

then what what is so bad in interfaces

because the whole goal of interfaces is

abstraction, abstraction and

abstraction. So again this answer is

technically right but it is not the main

thing. It is more of a byproduct. It is

a byproduct answer. Again when the

interviewer asks about saying that where

have you used delegates developers try

to create you know some kind of a

unnatural artificial forced answers like

I have used delegates here I have used

delegates there right but frankly ask

your heart and write down on the

comments below that many many of us

don't even use delegates definitely we

use different forms of delegates

probably we use events we use action we

use funk we use predicate we use lambda

expression

But directly delegates is a very rare

scenario right. [snorts] So when you are

also truthful and more natural right the

interviewer does connect to you. So when

you say that no like I have not used

delegates but yes when I double click on

a button I see a plus equal to which is

an event right. So try to answer again

you know answers which are more

practical in nature wherein you get more

connected with the interviewer rather

than trying to form up an unnatural and

an artificial answer and this whole

discussion of delegates goes into a

different tangent into a different loop

when the question of events come in and

when the question of events come in

right the the developers answer so

confidently so sophisticatedly right

saying that okay what is the Event event

is a encapsulation over delegates. Event

is a pure publisher subscriber

mechanism. Events actually help you to

implement a broadcasting kind of an

architecture. So remember all of these

answers are right. The only point is

that are you able to explain the

interviewer what exactly is a pure

publisher subscriber mechanism that is

important right? So yes, when you're

answering these sophisticated

when you're using these sophisticated

vocabulary, these sophisticated

technical vocabulary, make sure that you

are able to communicate with the

interviewer that what exactly are these

words and the interviewer can take you

for a ride. Specifically, if you look at

the multiccast delegate and event right,

they look very similar because in case

of multiccast delegate also you can do a

plus equal to and a minus equal to. You

can have a publisher subscriber

mechanism and in events also you can do

that right. So if you know the answer

write down on the comments down below

that what is the difference between a

multiccast delegate and a event remember

I'll just give you the answer the answer

is pure

pure publisher subscriber mechanism and

remember if ever those four rudra aars

of delegates that is funk lambda

action predicate if all of these come in

right then it becomes very very

different scene altogether you will see

a huge thunder dance all together.

Right? So remember that all of these

four things or even the five things

events, funk, lambda, action, predicate

are nothing but they are derived from

delegates. So that is very important to

remember. The whole point of this video

is that to make you realize that when

interviews are happening, right,

interviews should get converted into a

conversation. It should not be Q&A,

right? It should not be having more

academic answers. If you really want to

win the interviewer's heart, right? Your

answers should be practical. Your

answers should not lead to more cross

questions. For example, I talked about

delegate. If you say delegate is a

pointer to a function, then there is

another question and another question.

But when you say delegate is a call back

must be it just hits you know where it

wants to hit, right? So try to see that

in in the interview try to make an

interview as a conversation. So that

brings us to the end of this video. My

whole goal of this video was to give you

an essense of how interviews actually

happen and sometimes we don't even know

that the answers what you're giving out

there is it really impressing the

interviewer or is it really going in a

loop right so I hope that you got the

context of this video uh and thank you

very much and remember you can go to

quest.com you can look at our videos

what we have you can look at our live

trainings what are happening remember

one of the live trainings which I'm

coming around at this moment is

interview preparation course right so

must be you can have a look at that so

we have interview preparation course we

have the Azure course we have

microservices uh we have the IML course

for C# developers we have so many other

courses out there go ahead go to

queston.com and you can chat over there

thank you very much happy learning happy

job hunting