On Fri, 21 Sep 2007 15:06:28 +0200, Per Bolmstedt <[EMAIL PROTECTED]> wrote:
>Bob Provencher wrote: >> Well, if it's for a junior programmer they might not have a lot of design >> experience, so asking them to solve a coding problem working it out in front >> of you, and thinking out loud, will reveal a lot about how they think. So I >> wouldn't call this "stupid" (in fact I think that's uncalled for). > >.NET is a framework, not a programming language or a programming environment. >There are several underlying principles behind the framework, most of which are >well known design patterns. There are also programming methodologies and design >choices. And unless you understand all of these, you will never excel at .NET >implementations, whether it's ASP.NET or a fast atoi written in CIL. > >You should preferably interview people with experience of the .NET framework >(or Java, since that seems to be the what v1.0 copies), if the .NET framework >is that they're going to be working with. This means you should find out about >their relation to the framework. Do they understand it? Do they approve of it? >Do they think it's a steaming pile of Microshit? > >Personally, I would write down some of the core concepts of the .NET framework >(design patterns, programming methodologies, solutions to common problems, etc) >and base questions on these concepts. Anyone can learn how to rapidly count the >number of set bits in a byte given a certain programming environment. > >For example, you might want to talk about how .NET solves the various >challenges regarding globalization. This might include talking about Unicode, >encodings, strings, characters, databases, etc. > >Also, you might want to talk about OOP in .NET in general, and choose some >specifics, like events, exceptions, base classes etc. > >You might also want to talk about concurrency in .NET; threads, thread pools, >delegates, locking, monitors, etc. > >Perhaps you could formulate simple problems around these concepts to see if the >applicant thinks in a way that relates well to the .NET framework. Not all good >C programmers would make good .NET programmers. > > >On a side note, could we stick to a single quote style within the same message? not sure what this means... >First replier gets to choose? I have interviewed before and made some good decisions and some bad ones. But people basically overestimate the importance of knowing the intracacies of dotNet, OO (especially OOA/OOD), formal processes....and basically all the other stuff that people seem to make money out of writing books about. Not all good C programmers will make good dotNet programmers....but I think you'll find it's a pretty high correlation, if they can't write simple procedural applications then they wont stand a chance writing complex OO ones. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
