7 ms·
Mmmm, I interpret this practice a little bit differently. I wouldn't hire someone who isn't passionate about programming. Many of the people I work with today
by potatolicious 17y ago
Mmmm, I interpret this practice a little bit differently.
I wouldn't hire someone who isn't passionate about programming. Many of the people I work with today rarely code outside of work - kids, hobbies, friends, etc. This is okay.
But what you really want is one of the guys who stayed up all night in college to bang out the latest and greatest piece of code. You want the people who genuinely love doing this - because there are twice as many people who slummed their way through CS doing the bare minimum necessary.
I work with both types, and as the former type I cannot stand working with the latter.
- bdotdub 17y agoI agree completely. I don't think it should be how many hours you put into a side project or how much time you spend coding something outside of work. It comes down to whether the person really enjoys tinkering with (new) technologies. It shouldn't matter if you don't code outside of work and it isn't your employers business. But if you do code outside of work, it definitely says a lot about your character and how you regard technology. My coworker said to me once, "There are those who do technology as a job, and there are those who do it as a passion. We want the latter"
- gaius 17y ago"There are those who do technology as a job, and there are those who do it as a passion. We want the latter" Every company wants the best employees, but how many want to pay the best salaries?
- Retric 17y agoNone of the top programmers I know code outside of work. They all have other hobbies and have been coding for long enough that they no longer find it challenging. They enjoy coding, but passion burns out before you truly master software development. PS: There is a tendency to start doing side projects if there job stops directly involving coding because they start managing people, teaching, or just retire.
- _pius 17y agoNone of the top programmers I know code outside of work. Ironically I've had the exact opposite experience. In professional life, the best I could say about any programmer who doesn't code in their spare time is that they're "ok." And more often than not, I'd call them pretty mediocre. I've yet to meet anyone great who doesn't do at least a little programming on the side. It's a great predictor of ability in my experience. No offense to anyone here.
- timr 17y ago"Ironically I've had the exact opposite experience. In professional life, the best I could say about any programmer who doesn't code in their spare time is that they're "ok." And more often than not, I'd call them pretty mediocre....No offense to anyone here." Saying that you didn't intend to offend doesn't give you carte blanche to say offensive things. I'm one of those guys who doesn't code outside of work. I have a limited capacity for that kind of intense thinking, and since I'm using that capacity at work, I have to take time away to stay sharp. It's stupid and shortsighted to conclude that this makes me mediocre, even if everyone else in your limited life sample has been mediocre. Also, for the record? Nothing you wrote was ironic.
- staunch 17y agoI think your hostility is a bit overboard... The idea that doing intense work could sap your energy totally matches my experience. I would find it hard to believe that you love solving problems with code, but never find the opportunity and necessity to do that outside of work. For periods of months perhaps? Sure, but over years? Never doing anything other than what's expected at your job? I'd find that hard to believe.
- timr 17y agoI didn't say that I never "found the opportunity" to solve problems with code outside of work. I said I didn't have the energy to code outside of work. Your incredulity concerning that fact is irrelevant to my ability.