3 ms·
I must say, I agree. Having _no_ interest in programming outside work begs the question: Why is it your day job? Although I don't work on too many spare projec
by henriklied 17y ago
I must say, I agree. Having _no_ interest in programming outside work begs the question: Why is it your day job?
Although I don't work on too many spare projects on my own, I read a whole lotta websites relating to programming (this site, for instance..) and catch up on relevant news and technologies.
If the title was "No, I wouldn't hire a programmer who isn't cranking out code every hour he's awake", I'd definitely disagree. But, in my opinion, in this business, you really need to know what's going on. And unless you're in a research position at your day job, I'm guessing your boss wouldn't want you to spend working hours studying every interesting story on HN. Ergo, you'd read up on your spare time.
That's not to say you shouldn't have hobbies. A three year old Norwegian study [1] shows that IT-engineers have the largest burnout-rate of all occupations. It's important to relax, find something that makes you feel disconnected (my love for the moment is mountain biking, but whatever floats your boat).
[1] Google translate of Norwegian article about burnout-rates in the IT-industry: http://bit.ly/it-burnout http://bit.ly/it-burnout
- turtle4 17y agoYou ask "Why is it your day job?" Because I spend the largest part of my life at my day job, and want to work on something I am passionate about during that time. However I am also a person with many additional interests and desires, such as playing sports, reading, art, and music and since each of those are deep areas of interest themselves, they all occupy parts of my non-working life, while being balanced with my family. There are plenty of people who feel this way. They are well balanced individuals who are effective at their jobs, and passionate about them. But there are only so many hours in a day. Working isn't just about time spent coding. It is about working well in a team, and relating with your customers, and understanding social issues as well as technical ones. Someone who only codes is simply more likely to be underdeveloped in one of those areas. It is just a stupid qualifier. If you are hiring a marketer, would you only hire someone who telemarkets from home on their off time because they enjoy it? That's just stupid. Someone who has side projects at home -might- be a more experienced developer. Or they could be a poorly rounded individual. Someone who doesn't work on side projects at home -might- be non-passionate. Or they might be very passionate and effective, and simply more well rounded. To say you would always require one or the other is just dumb.