Earlier quoted context omitted.
> Can you imagine "if you are studying art and want a job as an artist, you'd better be doing drawing and uploading to deviantART in your free time. Otherwise you're just not cut out for this career." Yes. Yes, I can absolutely imagine judging someone in a partially-artistic field on whether they enjoy making art on their own time. That doesn't apply in every field, sure, and I bet chip designers don't generally go h…
I absolutely agree that when hiring an artist, you want that person to be excited about art. I suppose in a nutshell, my thought is: all time is your own time. Choosing to pursue a career in is a monumental investment of your own time into . We ought not judge as terribly different those who spend ~50 hours a week of their own time doing X and getting paid for it and those who spend ~50 hours per week of their own ti…
But back to the career professional context. I think maybe I've identified the disconnect. Could it be that asking about personal projects is a way of identifying not just a competent developer but an actual geek? Those are different roles with different requirements. For example, you probably don't want to unleash a geek on your legacy business logic maintenance project. They'll probably be bored and end up breaking stuff in the name of optimization or cleanup. Similarly, you don't want "just" a programmer in your R&D team where you genuinely want and need creative innovation.
So maybe both sides are correct: for some jobs, it's completely appropriate to expect personal projects. For others, it shouldn't be expected at all. What do you think?