4 ms·

Funnily enough, I find myself the exact opposite. Give me a really hard engaging problem and I can work 16 hours and barely realize any time has passed, but spe

Funnily enough, I find myself the exact opposite. Give me a really hard engaging problem and I can work 16 hours and barely realize any time has passed, but spending even 1-2 hours on something rote saps my energy for the entire day. My tolerant is even lower for the particularly challenging combination of tasks that are both uninteresting but also tedious.

jacquesm 4y ago
The payback of such stints can be brutal though, and it won't necessarily happen the next day either.
jll29 4y ago
So true. Annual tax return? Expense reclaim forms? Administrative faculty meetings? - All so bad that the most productive folks can turn into procrastinators.
Retric 4y ago
I don’t think we are talking about the same kind of difficult vs straightforward problems. Think professional chess players. While prepping they can spend very long hours playing/studding high level chess but tournaments are another level. Challenging is fun, the limits of human ability are always stressful. People can run for 11 hours in an ultra marathon but they can’t do it at 13+ mph pace of a half marathon.
- underdeserver 4y ago
  Exactly. To me the difference is in scope, familiarity, and stress. While I'm doing the task: 1) Do I have to hold 15 interdependencies in my head? 2) Is this something I did a million times in the past and do I already know exactly what the failure modes look like? 3) Is this something high-stress, e.g., is this the big project that's supposed to make my team look good or net me a promotion? Wiring in a UI for a sophisticated CRUD can take 10 hours but it doesn't _really_ have that many interfaces, I've done it a million times, and nobody getes excited about it. It's just something you do. Building a billing pipeline for a product is something I've never done before, is very-high-stakes for the business, and can go wrong in a bazillion ways, many of which are not my fault. There's no way I can imagine getting more than an hour or two of work on this per day.
bryanrasmussen 4y ago
rote work is not what was talked about though, yes rote is boring and tiring, a hard engaging problem (engaging meaning something you are interested in I take it) can keep one occupied. This is what I describe as the artistic personality type in programming, doing great impressive work when interested, awful crap work when not interested. but what about a hard problem that you do not make any progress on and you are sure what you did should solve it and what is wrong, why is it not working? You can't say it's uninteresting, but it is debilitating.
birksherty 4y ago
Once in a while it might be true. But this post is about job. Doing that for 8-16 hrs often will burn out and later I'd avoid such jobs.
adql 4y ago
I was like that, now it kinda only works for something I'm really passionate about

jacquesm 4y ago

The payback of such stints can be brutal though, and it won't necessarily happen the next day either.

jll29 4y ago

So true. Annual tax return? Expense reclaim forms? Administrative faculty meetings? - All so bad that the most productive folks can turn into procrastinators.

Retric 4y ago

I don’t think we are talking about the same kind of difficult vs straightforward problems. Think professional chess players. While prepping they can spend very long hours playing/studding high level chess but tournaments are another level. Challenging is fun, the limits of human ability are always stressful. People can run for 11 hours in an ultra marathon but they can’t do it at 13+ mph pace of a half marathon.

underdeserver 4y ago
Exactly. To me the difference is in scope, familiarity, and stress. While I'm doing the task: 1) Do I have to hold 15 interdependencies in my head? 2) Is this something I did a million times in the past and do I already know exactly what the failure modes look like? 3) Is this something high-stress, e.g., is this the big project that's supposed to make my team look good or net me a promotion? Wiring in a UI for a sophisticated CRUD can take 10 hours but it doesn't _really_ have that many interfaces, I've done it a million times, and nobody getes excited about it. It's just something you do. Building a billing pipeline for a product is something I've never done before, is very-high-stakes for the business, and can go wrong in a bazillion ways, many of which are not my fault. There's no way I can imagine getting more than an hour or two of work on this per day.

bryanrasmussen 4y ago

rote work is not what was talked about though, yes rote is boring and tiring, a hard engaging problem (engaging meaning something you are interested in I take it) can keep one occupied. This is what I describe as the artistic personality type in programming, doing great impressive work when interested, awful crap work when not interested. but what about a hard problem that you do not make any progress on and you are sure what you did should solve it and what is wrong, why is it not working? You can't say it's uninteresting, but it is debilitating.

birksherty 4y ago

Once in a while it might be true. But this post is about job. Doing that for 8-16 hrs often will burn out and later I'd avoid such jobs.

adql 4y ago

I was like that, now it kinda only works for something I'm really passionate about