4 ms·
The problem with rating a candidate on the basis of his personal/home projects is that it excludes potentially-excellent candidates who are __unable__ to work o
by acuozzo 13y ago
The problem with rating a candidate on the basis of his personal/home projects is that it excludes potentially-excellent candidates who are __unable__ to work on anything at home due to, e.g., having several young children and half-dead parents to care for.
(Also, don't try to retort with "so ask them about the personal/home projects they did before having kids", as that wouldn't be sufficient to cover the people who have had children at a young age; e.g., before turning 20 years-old.)
- aestra 13y agoOr how about those potentially-excellent candidates who don't have children but just have a life? I love my job. I love writing code. I am passionate about it. The time I spend at work I mostly enjoy, but 40 hours a week is enough for me. I would rather spend the rest of my time with the people I love or on other ventures that don't involve sitting in front of a screen. If you don't want to hire me because my job isn't my entire life, than I don't want to work for you. Nobody should be penalized career-wise for enjoying their free time.
- auggierose 13y agoNever seen that. All people I know who love programming even find time to do their own stuff on a 60 hour schedule.
- acuozzo 13y agoI love programming, but I love my hobbies (e.g., film and video preservation) A LOT more. I don't love programming enough to devote time outside of my 40 hours/week to it.
- auggierose 13y agoAnd just to avoid misunderstandings: I don't think that 60 hour schedules are good! Personally, I prefer a 25 hour week of coding only on my own stuff and 0 hours of coding for other people :-)