Just sayin’…

(why waste time coding an algorithm (or cpu time executing it) to calculate a value that is already known?)

It was an interesting challenge.

public class Course
{
public int room;
public string name;
public Course(int room, string name)
{
this.room = room;
this.name = name;
}
}
public interface Role
{
string Name { get; }
}
public class StudentRole : Role
{
public string Name {
get { return “Student”; }
}
}
public class LecturerRole : Role
{
public string Name {
get { return “Lecturer”; }
}
}
public class JanitorRole : Role
{
public string Name {
get { return “Janitor”; }
}
}

public class CourseAttending
{
Course course;
Role[] roles;
public CourseAttending(Course course, Role[] roles)
{
this.course = course;
this.roles = roles;
}
}
public class Person
{
public string name;
public CourseAttending[] coursesAttending;
public Person(string name)
{
this.name = name;
}
}

public void Main()
{
Person person = new Person(“John”);
Course course = new Course(101, “WWW”);
person.coursesAttending = new CourseAttending[] { new CourseAttending(course, new Role[] {
new StudentRole(),
new LecturerRole()
}) };
}

Can’t develop without it… Thanks

The problem with these tests is that it’s treating the process backwards. If you want someone who is really good at what they do, no matter what discipline you’re hiring, they have to choose to work for you. You want it to be as easy as possible for them to find you and get through the interview process while still filtering out the people you don’t want. Good people do not need a job, they already have one. The more hoops you make them jump through the less likely they’ll bother to keep going. This is why tests like ‘reverse a string’ or fizzbuzz are great. They’re easy to understand, fast to implement, and shouldn’t require any outside resources if you allow the interviewee to use whatever language they want. Then you give them a complex problem and have them work through some general design and implementation ideas without talking about code to make sure they can manage some high-level design. Between these 2 types of tests you should be able to filter out the non-programmers while not putting up too many roadblocks to deter someone who needs to choose to work for you.