3 ms·
Three things come to mind (explanations follow): 1) Does the programmer _complete_ interesting programming projects in their spare time? 2) Can the programm
by spaghetti 18y ago
Three things come to mind (explanations follow):
1) Does the programmer _complete_ interesting programming projects in their spare time?
2) Can the programmer explain something mildly technical such that you, the business guy, can understand?
3) A test: push the programmer a bit. Act as if you don't understand something and be a bit rude. If the programmer does anything except listen to you and patiently try to help you then he/she is no-hire.
Explanations:
If the programmer doesn't complete interesting projects in their spare time they don't have enough passion for programming.
If he/she can't explain something clearly it's highly likely they can't communicate with business folks effectively in general hence they're not going to be effective at the job.
There's a lot of angry programmers. If the programmer becomes visibly annoyed or angry during an interview you've found yourself a no-hire. Angry programmers destroy morale very quickly.
That's my opinion on how to find "good" programmers. Keep in mind the percentage of "good" programmers who will be a good fit for your business is small. This is where respectful drilling of technical matters is appropriate. This part of the interview is completed by a _technical_ employee. Remember that lots of good programmers can fail technical interviews because they just don't know the particular technology.
- ilaksh 18y ago1) I have completed some. I have started many more than I completed. More of my energy goes into making sure I complete projects I am actually getting payed for. Also, I could say that it was complete any time I wanted, but what fun would that be? 2) Good point. 3) If someone pushes me rudely then I am going to get mad at them and they will know it because I am human and I have every right to get angry. I don't like to put up a front. This is why I'm a programmer and not a salesperson, executive, or someone who's job it is to be two-faced. Does that mean I won't continue to try to help a rude person that genuinely needs help and that is not just trying to manipulate me? No, but that's a different situation. 4) If they become angry or annoyed because you were deliberately rude like you suggested above, then it doesn't make sense to eliminate them for that reason. If you were polite and human and ordinary conversation angered them, then that is a red flag that no one needs you to point out. 5) I have a feeling if I interviewed with you for more than thirty seconds I would come off as another one of your angry programmers, because I would be at that point. 6) Respectful drilling of technical matters: i.e. programming languages and API pop-quizzes? "Respectful" drilling? What does a verbal pop-quiz have to do with programming? What about this part: do your existing programmers and managers like the person? What is your name so I can avoid ever working for you?
- donaq 18y agoPerhaps a 1) could be better served with asking a programmer why they started said interesting programming project. If they started a project for the specific purpose of learning a particular skill and they've already learned it, it would make no sense for them to complete it, I think. For example, I once started a bittorrent client in C just to learn how to use sockets and pthreads in C as well as understand the bittorrent protocol. While I never completed it (what would have been the point? there are already way too many out there and I did not have a unique take on the idea), I did accomplish what I set out to do.