What are Good Things to Know in a C# Interview?
-
What are Good Things to Know in a C# Interview?
Off the top of my head, I have come up with this list:
* SOLID mythodology.
* Dependency Injection
* Levels of Try, Catch, throw, and finally statements and how they work
* The tenants of Object Oriented Programming such as polymorphism, enacpsulation, etc.
* Unit Testing (are interfaces used somehow)
* The difference between an abstract class and interface
* garbage collection and when to override or overload it
* difference between override or overload
* Is there inheritance in C# ?
* What is an interface used for?I am posting this here to see of anyone can add to this list. I am asking about general topics, not specific interview questions.
-
What are Good Things to Know in a C# Interview?
Off the top of my head, I have come up with this list:
* SOLID mythodology.
* Dependency Injection
* Levels of Try, Catch, throw, and finally statements and how they work
* The tenants of Object Oriented Programming such as polymorphism, enacpsulation, etc.
* Unit Testing (are interfaces used somehow)
* The difference between an abstract class and interface
* garbage collection and when to override or overload it
* difference between override or overload
* Is there inheritance in C# ?
* What is an interface used for?I am posting this here to see of anyone can add to this list. I am asking about general topics, not specific interview questions.
"Why did you bother to learn 'interview question and answer' stuff, since the follow up question will just show you don't know anything in any detail?" Forget them: know your subject and apply for jobs you can do instead of ones you can't ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
What are Good Things to Know in a C# Interview?
Off the top of my head, I have come up with this list:
* SOLID mythodology.
* Dependency Injection
* Levels of Try, Catch, throw, and finally statements and how they work
* The tenants of Object Oriented Programming such as polymorphism, enacpsulation, etc.
* Unit Testing (are interfaces used somehow)
* The difference between an abstract class and interface
* garbage collection and when to override or overload it
* difference between override or overload
* Is there inheritance in C# ?
* What is an interface used for?I am posting this here to see of anyone can add to this list. I am asking about general topics, not specific interview questions.
A completely useless endeavor as there are thousands of possible interview questions and you can't memorize it all. Part of the interview process is how you handle (and answer) questions you don't know the answer to.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak -
What are Good Things to Know in a C# Interview?
Off the top of my head, I have come up with this list:
* SOLID mythodology.
* Dependency Injection
* Levels of Try, Catch, throw, and finally statements and how they work
* The tenants of Object Oriented Programming such as polymorphism, enacpsulation, etc.
* Unit Testing (are interfaces used somehow)
* The difference between an abstract class and interface
* garbage collection and when to override or overload it
* difference between override or overload
* Is there inheritance in C# ?
* What is an interface used for?I am posting this here to see of anyone can add to this list. I am asking about general topics, not specific interview questions.
If you can't answer, you liable in the Nerherlands. I know, I caused damage north of 14k Euro, including overtime.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
A completely useless endeavor as there are thousands of possible interview questions and you can't memorize it all. Part of the interview process is how you handle (and answer) questions you don't know the answer to.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave KreskowiakThis. I have a couple of topics (IDisposable and async). I do warn up front that my goal is to see how they reason about things they do not know for sure, so they should expect I ask them things they do not know. I give this warning as the goal is not to test how they deal with panic, but how they reason. While it can be nice to test how people deal with panic, it is luckily not something we need resilience against on a daily basis - so reasoning is more important. The nice things about these topics is they are simple on the surface but quite complicated once you dig into them. So the topics works for juniors as well as people with a lot of experience.
-
This. I have a couple of topics (IDisposable and async). I do warn up front that my goal is to see how they reason about things they do not know for sure, so they should expect I ask them things they do not know. I give this warning as the goal is not to test how they deal with panic, but how they reason. While it can be nice to test how people deal with panic, it is luckily not something we need resilience against on a daily basis - so reasoning is more important. The nice things about these topics is they are simple on the surface but quite complicated once you dig into them. So the topics works for juniors as well as people with a lot of experience.
Thanks anyway:thumbsup:
