[bonniemuffin]

I definitely don't want my team to appreciate boring tasks! I want them to persist, endure, and then automate.

The person who grinds through the boring stuff while thinking about how to automate it so they don't have to be bored anymore, is the person I want to hire.

[WalterSear]

The nature of the work doesn't allow that. Coding takes all your thought - even when it's boring and monotonous.

The comparisons being made to washing dishes aren't realistic.

[bonniemuffin]

Sorry for the ambiguity: I didn't mean literally at the same time like washing dishes while dreaming of dishwashers. I mean, like, do some boring coding drudgery one day/week/month, and then the next day/week/month do a bit of dreaming and whiteboarding of how to automate a better world, and then we can prioritize and make time for the automation work to make the better world a reality.

The important part is noticing and recognizing things that are ripe for automation, rather than accepting the shitty world as it is and continuing to suffer through repetitive work that could've been automated.

[dageshi]

I agree with this, boring & monotonous code tasks are basically excruciating because you've got to concentrate on them hard and yet you'd rather be doing just about anything else.

[nradov]

I've done some refactoring work that didn't take any more mental effort than dish washing.

[WalterSear]

Sure. Is most work like that, though?