That's the thing - I'm not sleep-deprived (except on occasion by choice) and I'm quite healthy and happy. I like to think I'm reasonably productive. Sure, output depends on how I'm feeling, but I still would rather be working than not.
You know what it is? I get paid money to play with computers. As much as I want to think of what I do as work, I come back to the fact that I'm lucky enough to have made my hobby a profession. Do I think that everyone in technology is in the same boat? No. Not by a long shot. But would I happily swing by on a Sunday to help a coworker with a problem, you bet. I love hard problems. Hard problems I get to solve by using technology are even better. I choose to surround myself with those individuals who feel the same way, I don't see why that is a bad thing.
Playing with computers is awesome. Coding is awesome. It's always a huge boost to put something new out to the world. It's great.
But you know what else is awesome? Spending time with my wife, gardening, hiking, traveling, biking, eating, exploring, wine, beer, home improvement, etc.
So yeah, I will never come to the office just to hang out with someone...especially on a sunday. But I'll get my work done and help others get their work done and it will be good work. I just won't do it on a sunday.
- Ok, a year and a half ago I worked 43 straight 10+ hour days because I really believed in what I was doing. Chances of me ever doing that again voluntarily? Basically nil. Life's too short and spending so much of it in front of a screen...yuck.
There is a difference between coding on my own vs. coding for company.
I rather work on learning about Minix, Linux Kernel, 3D graphics rendering, compilers, Bioinformatics than messing with some config file because a production server was upgraded from Stack 1.1 to 1.11 over the weekend.
Company's goal is to serve the business no matter how intellectual my co-workers may be or the technology involved. My goal is to learn for the fun of it.
Comments
That's the thing - I'm not sleep-deprived (except on occasion by choice) and I'm quite healthy and happy. I like to think I'm reasonably productive. Sure, output depends on how I'm feeling, but I still would rather be working than not.
You know what it is? I get paid money to play with computers. As much as I want to think of what I do as work, I come back to the fact that I'm lucky enough to have made my hobby a profession. Do I think that everyone in technology is in the same boat? No. Not by a long shot. But would I happily swing by on a Sunday to help a coworker with a problem, you bet. I love hard problems. Hard problems I get to solve by using technology are even better. I choose to surround myself with those individuals who feel the same way, I don't see why that is a bad thing.
Playing with computers is awesome. Coding is awesome. It's always a huge boost to put something new out to the world. It's great.
But you know what else is awesome? Spending time with my wife, gardening, hiking, traveling, biking, eating, exploring, wine, beer, home improvement, etc.
So yeah, I will never come to the office just to hang out with someone...especially on a sunday. But I'll get my work done and help others get their work done and it will be good work. I just won't do it on a sunday.
- Ok, a year and a half ago I worked 43 straight 10+ hour days because I really believed in what I was doing. Chances of me ever doing that again voluntarily? Basically nil. Life's too short and spending so much of it in front of a screen...yuck.
There is a difference between coding on my own vs. coding for company.
I rather work on learning about Minix, Linux Kernel, 3D graphics rendering, compilers, Bioinformatics than messing with some config file because a production server was upgraded from Stack 1.1 to 1.11 over the weekend.
Company's goal is to serve the business no matter how intellectual my co-workers may be or the technology involved. My goal is to learn for the fun of it.