4 ms·
I think the impressive thing is doing it day after day. I can do lots of things, including programming, for 12+ hours. The trouble is, after a day or two of tha
by handrous 5y ago
I think the impressive thing is doing it day after day. I can do lots of things, including programming, for 12+ hours. The trouble is, after a day or two of that, I desperately don't want to do whatever-it-is for several days or weeks. I want to go do other stuff.
It's the doing it day after day on a regular schedule that makes me feel like I never really recover from programming, and just want to zone out and stare at the wall until bed time, having very little energy left for anything either fun or productive, after 4-5 hours, most days.
I'll even do that with video games. Get the family out of the house and give me a weekend, I'll play vidja games for like 16 hours. Then wake up the second day and not want to touch a game for at least a week, and instead start doing home improvement projects or whatever. Or sit outside and read a book all day. Not because I feel like I should, but because it's the thing I most want to be doing, and I have zero desire to look at a screen for a good long while.
The regularity of work is what makes it so damn draining, for me. I'm sure it'd ruin gaming for me in short order, too, though I'd have fared a lot better at it back when I was in my teens or early 20s than I would now, for sure. I can't do 30 waking hours of anything now. 24 just about ruins me. I could get to about 36-38 before hitting a wall and passing out for like 12 hours, back then. 30 wasn't that big a deal, and I hit that mark pretty often (usually, yeah, playing video games for a good chunk of it).