aDemoUzer

was able to get it running on windows, so I am happy with it. Needs more in-depth guide so I know what it provides and the reasoning behind ur "sane defaults"

good job on the mashup, even I like it. Wish you could hear it through my ears, it sounds really good.

need to provide description of what tasks you need to get completed by the freelancer.

www.locu.com does not works, locu.com works. You may be missing DNS config for www.

It is not a problem. Let's move on.

Applied as no-idea, single founder => no cigar.

good to hear. I had tried THunderbird in the past but it would just crash. Just started today for first time in a year and just upgraded from V7 to v11. Working good so far.

Submitted as a lone founder with no-idea - I probably have like 2.3% chance :p

In my view the interviewer has made biased assumption: IF someone who cannot give concise and clear questions about the concept THEN they don't know about it.

You can consider it a shortcoming on my part or reality for most programmers, but I don't tend to memorize names of concepts, I just know how to use them. i.e. I may be using inheritance or polymorphism in my code, but my brain does not every time thinks about what these terms mean and am I applying them as they are defined. I have been programming for years and OOP has become second nature to me; I know how to apply OOP, but have long forgotten most of the terms.

In my view, when interviewing, the questions should be practical problem so it tests user's ability to program a solution, not about being able to churn out the definition. Example: If you want to test someone's OOP expertise, give the person a list of classes and ask them to create a UML or how they would structure their classes. Example 2: Give them a problem like, create 2 classes: Animal and Dog. All animals have a name and a dog can bark. Test to see if the programmer would extend Animal class from Dog class, or maybe he decides to make an Abstract class out of Animal class.

The only downside of these questions is that you would need to have interviews who are competent in the OOP concepts themselves. Continuing to ask dictionary questions is a cop-out solution to not having technical interviewers and it is easier for someone to check if interviewee is able to mention some of the keywords that are in the definition you found on wikipedia.

Unfortunately, you will continue to reject most developer job applications and miss out on lot of great candidates.

my opinion on re-learning - there were multiple subjects that I took in college which went over same content that I had learned in High School. I actually enjoyed re-learning them because the content was presented in a different way, so it made more sense to me that it had before. It is one thing to learn something once, but when I learn some concept over and over again, I tend to discover something new about it or related to it. Even small concepts can have greater meaning to it that I did not saw at first.

I have similar experience with movies - Dark Knight - I watched it 4 times and each time I find it more fascinating because I saw new details in the movie.

Not fond of the idea and I just did not get inspired nor saw its potential.

For next batch, I applied as lone founder with no-idea, if you did not get in, seems like I might have similar fate.

C makes me the most sad to use. It is only useful if I want to high performance apps - since I don't need to, I don't use it as much. When I did had to work in for school projects, I just hated the part that I had to write so much code just to do simple things.