Link Details

Maybe those people are to busy thinking on abstractions and frameworks that already does all the OOP for you than simple OOP questions that maybe they learned in high school and now they just forgot.

People like you just let go bright people really, The selection employment system is broken.

What would you rather have than selection? Employ everyone?

Come on! This was a syntax quirk, and not knowing the answer does not mean a thing.

But what you are saying about people thinking about frameworks and abstractions, these are not those people. I dont ask people who understand abstraction well questions like what is the c# syntax of this.

Syntax quirk of C#. Knowing it proves nothing of one's ability to produce high quality code

The real irony here is that the question is a perfect example of how to do things the wrong way.

I completely agree. How to write sensible comment to this property?

/// >
/// Gets or (maybe) sets someting.
/// >
public int MyProperty
{
....

As I have commented on the post that, this syntax proves nothing, nearly all devs failed to answer this question. But that did not stop me from testing them out more. So I was curious and wanted everyone to know this.

However when I am looking to hire someone who can understand my instructions such as: "Make compoment A instansiation factory based and make sure you have the exportable classes exposed via public interface with their scope being private". How do get that done if the developer do not understand design patterns or difference between interface and abstract classes?

It might help if you understood those terms well enough to use them.