6 ms·
I would go for pair programming.
by maxxxxx 9y ago
I would go for pair programming.
- kabouseng 9y agoThe danger with pair programming is you easily get a partner who sees the activity as a competitive exercise / dick measuring activity* , and some engineers find enjoyment in proving to everyone else (including new hires) their superiority. *excuse my language, but it is the most accurate description I could come up with.
- arthur_pryor 9y agoi'd posit that if an employer can't find a decent pool of current employees to potentially pair program with an interviewee, they have deeper problems than getting that upcoming interview right, and need to correct for some past hiring mistakes ASAP. i would definitely be looking for employment elsewhere if i my co-workers were so unpleasant that i thought they'd turn every pairing session into a pissing contest (and i say that as someone who generally prefers solo programming as far as immediate enjoyment goes, but who finds that pairing is often useful and/or necessary).
- AFNobody 9y agoAnd then you know that employer has issues and to avoid them.
- jaggederest 9y agoYep. Exactly. Pairing is a two way street.
- maxxxxx 9y agoIdiots have a negative impact on any type of job search. I have been in interviews where I showed a valid solution for a problem but failed because it wasn't exactly the one the interviewer wanted. On the other hand if I did pair programming with somebody and it worked well this would be a strong indicator for a healthy comonay culture.
- majewsky 9y agoThat's actually another reason why pair programming is good: The interview is just as much a signal to the candidate as it is to the employer. If the developer he's pair-programming with is a douche, it's a good sign for the candidate to run and not look back.