|
|
Wow, spooky case of paradolia
- looks like a partially obscured face just a tad right of the center (mouth, nostrils, part of the left eye) - face of God?
Sin tack ear lol
Pressing the any key may be continuate
|
|
|
|
|
I am conducting a round of interviews this week, looking for a mid-level C# developer. I'm down-selecting some tech questions which are aimed at trying to filter out the "Yeah, I did a C# project a couple years ago" crowd from the "C# has been in my blood for at least a year or two" folks.
But selecting appropriate questions is always a challenge. (Just because something is obvious to me, doesn't mean every developer has encountered it. Every project is different and people get exposed to different things. I definitely want to avoid "language trivia.") So here is my first cut of questions. For those of you who are .NET devs, would you agree that somebody with a couple years of solid experience should be able to talk intelligently about most of these topics? (Not all of these are C#-specific.)
- How do you inherit a class, and why might you want to?
- What is the purpose of interfaces, and how are they helpful?
- Why would you ever want to make a method private or protected?
- When might you use a static class or method?
- Can you explain what a lambda is, and why you might use one. (Or, alternatively, LINQ?)
- Why might you use a property instead of a regular variable? (How are they different?)
- Are you familiar with any "Design Patterns"? Can you name one or two that you have used?
- Have you heard of the concept of "tight" or "loose coupling", and how does it effect code design?
- Have you used a Unit Testing framework? If so, how did it (or unit testing in general) benefit your code, if at all?
[Note: we have decided not to make the candidates write or debug actual code in the interview, with the possible exception of FizzBuzz. But that is a topic for another thread.]
modified 24-Jan-17 10:50am.
|
|
|
|
|
kdmote wrote: I definitely want to avoid "language trivia."
Well ... 1, 2, 3, and 4 are pretty much "language trivia" 
If I was you, I'd have a look for those "interview questions and answers" sheets some "developers" seem so fond of. Ask the questions on that and reject anyone who gives the answer on the sheet...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: 1, 2, 3, and 4 are pretty much "language trivia"
Really? I particularly liked those questions. What I liked about them was that, for the most part, there isn't really any right or wrong answers, per se, but I would be surprised if somebody had been doing development work for a year or two and hadn't encountered them in some form. I don't care about the exact syntax; I'm just interested to hear if they can discuss the concepts thoughtfully.
modified 24-Jan-17 10:51am.
|
|
|
|
|
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
|
Ask them, wether they prefer strongly typed or stringly typed code.
Edit: That typo was good 
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
modified 24-Jan-17 10:36am.
|
|
|
|
|
I prefer stryngly tiped code myself.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I prefer smugly triped.
This space for rent
|
|
|
|
|
How about boldly striped?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Afraid it's boldly gone where no code has gone before.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Since NextGen it's 'to baldly go where...' 
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
I prefer stringently-typed variables, myself.
Software Zen: delete this;
|
|
|
|
|
That's commendable, as long as you don't stringently stringly type.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
To weed out the truly weak, you could ask them how long they've been developing in "C hashtag"
|
|
|
|
|
In about the year 2000, after coding C++ for a few years, I saw C#. I pronounced it "see pound". I still don't know why it is "see sharp".
Alternatively, I think "see plus plus plus plus" makes more sense - it's almost a pound symbol.
++
++
|
|
|
|
|
Of course, it's just a fancy D-flat.
|
|
|
|
|
Pualee wrote: I still don't know why it is "see sharp".
Because in musical notation "#" indicates a "sharp" note: it's called an "accidental" that raises the pitch of a note by a semitone. Sharp (music) - Wikipedia[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Oh, I know music, just thinking about the progression of the language:
A, B, C, C++
Of course there is D but nobody cared.
C++ implied there was something more than C (the ++ operator for instance). By why switch to music for C#? We know the C part came to attract C and C++ developers, but why on earth "sharp"?
When using the # character in coding, it was always pound, not sharp (now folks fancy it a hash tag).
|
|
|
|
|
|
Not a bad set of questions at all - nothing too narrow in there.
If not getting them to write code, it might be a good idea to ask how they would approach writing something for a stated problem. In our last round of interviews (admittedly for a junior), I set what I considered to be a super-easy coding task. I thought at the time that it would filter out a couple of idiots but hardly any candidates even got close to it.
The task was simply to take an input of a sum of money and break it into the smallest number of notes and coins possible.
The first attempt was hilarious (pretty much if (amount == 52.31) print "some answer that added up to about £48") and they didn't get much better from there.
At one point I was so worried that I'd gone OTT that I asked my ageing mother. She worked out the algorithm in half a second.
The thing was, some of these guys could talk the talk (or at least quote Wikipedia) but couldn't code their way out of a wet paper-bag so I really would go with a test of that sort.
Slogans aren't solutions.
|
|
|
|
|
Is your mother available for an interview?
Seriously, though. I think that's kind of the problem with interviews: bright people can get so nervous that they aren't able to think as quickly or clearly as they might under normal working conditions. Good/bad interview performances don't always correlate to actual skill or aptitude. That makes it tough for an interviewer.
But I appreciate the suggestion.
modified 24-Jan-17 10:44am.
|
|
|
|
|
These are pretty good questions for a mid-level developer.
What I have found to be the best way to gauge a developer's skills is to ask them to tell you about different projects they have worked on. If they don't give much detail ask if they worked on it alone, if they wrote all the code or just maintained it, if they designed the classes etc. You should be able to tell if they are qualified by allowing them to do most of the talking.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
