Linked by Thom Holwerda on Fri 22nd Feb 2008 09:16 UTC, submitted by obsethryl
.NET (dotGNU too) "Previously, we have presented one of the two opensource licensed projects related to creating a C# kernel. Now it's the time to complete the set by rightfully presenting SharpOS, an effort to build a GPL version 3 + runtime exception licensed system, around a C# kernel of their own design. It is my pleasure and priviledge to host a set of questions and answers from four active developers of SharpOS, that is William Lahti, Bruce Markham, Mircea - Cristian Racasan and Sander van Rossen in order to get some insight into what they are doing with SharpOS, their goals, their different design and inspiration."
Thread beginning with comment 301993
To view parent comment, click here.
To read all comments associated with this story, please click here.
dagw
Member since:
2005-07-06

In the long run all I see emerging from this is something I don't really like, coders who say are experienced and perform horribly when needed to code in c++ and the likes.


This is simply solved by hireing people with the skills you actually need. If you need a C++ programmer hire someone with C and/or C++ experience. Expecting someone who knows how to 'program' to perform equally well at all programming tasks and in all languages is silly.

If I need someone to write numerical analysis software in C I wouldn't hire someone who's an expert at writing web apps in perl.

Reply Parent Score: 3

Yamin Member since:
2006-01-10

"This is simply solved by hireing people with the skills you actually need. If you need a C++ programmer hire someone with C and/or C++ experience"

As I've developed in the software engineering world, I've come to have an infinite amount of sympathy for hiring managers. It's virtually impossible to tell who is a good programmer. Much less what is 'experience'?

I'm worked at places with dead weight programmers who quite frankly are idiots. I'm sure their resume looks great with 10 years experience with Nortel (speaking as a Canadian...seen too many of these) or some other company.

I've met guys with 10 years c++ experience who still don't really understand how to program properly for it. On the other hand, a good engineer DOES investigate and make sure they understand the language before going into the code. For example, I used to be a purely c/c++ guy, but was eventually assigned to a c# project. I read up on it, made sure I understood it. Suddenly I start seeing fundamental flaws in how the project was currently written (by people with 3-4 years c# experience.

Also, c/C++ are not the same thing. Hiring someone with C experience to do C++ is a recipe for disaster. Just last night I spent 3 hours debugging a problem because someone forget to implement a c++ copy constructor for a class when using the STL. None of those terms mean jack for a C programmer.

So in conclusion. Hiring a programmer/software engineer is insane. There's no magic in it. I really think everyone should make use of that 3 month probation rule that comes with most contracts. If the person is not as capable as you thought, let me go in the first 3 months. If the worker doesn't quite like the workplace...they should feel no guilt leaving the company.

Reply Parent Score: 2

tomcat Member since:
2006-01-06

As I've developed in the software engineering world, I've come to have an infinite amount of sympathy for hiring managers. It's virtually impossible to tell who is a good programmer. Much less what is 'experience'?


Well, I half agree. It is certainly difficult to find good programmers -- but not impossible. My interviews are pretty thorough, and they definitely tell me whether a candidate has the technical proficiency to succeed in my org. HOWEVER, what's unknown are the intangibles: personality, fit, motivation, drive, etc. And, to some degree, it's the intangibles that separate the mediocre programmer from the amazing programmer. What usually convinces me are the things that a programmer does in his/her free time BESIDES their usual work. Let's face it: Outstanding programmers don't just confine their obsession to their 9-to-5 jobs. Usually, they have some kind of project outside of work; for example, a game or a prototype or whatever. When devs tell me that they don't do anything other than their work, it often raises a red flag in my mind. Not that that is the only data point, but it can be a significant one, if you are on the fence about a particular candidate. I like to see evidence of passion and drive and ambition. Granted, somebody could be blowing smoke up my ass, but it's usually possible to see through that nonsense by asking successively deeper questions; how did you solve X? did you think about Y? what kinds of potential changes would you make now? etc.

Reply Parent Score: 2