On a tangent, I was a bit confused by the everyday examples given in this article.
"We're often faced with similar trade-offs. You want a meal that's both cheap and delicious? A job that's both well-paid, easy, and fulfilling?"
I really don't feel like "easy" is a dimension I wish to optimize for in a job. It almost feels opposite to what I've actually optimized for - since for me a fulfilling job usually means full of deep technical challenges. I want a job without unnecessary friction, without interpersonal drama, even one that's low stress. But definitely not easy.
I get what you’re saying, but I wouldn’t say easy is the opposite of challenging. As a quick example, I would surely find a day job of manual labor harder and significantly less enjoyable than a day job of software engineering challenges.
(And please note that I do not mean to imply that there are no challenges in manual labor or that software engineering is more important.)
Agentlien · · focus · HN ↗
"We're often faced with similar trade-offs. You want a meal that's both cheap and delicious? A job that's both well-paid, easy, and fulfilling?"
I really don't feel like "easy" is a dimension I wish to optimize for in a job. It almost feels opposite to what I've actually optimized for - since for me a fulfilling job usually means full of deep technical challenges. I want a job without unnecessary friction, without interpersonal drama, even one that's low stress. But definitely not easy.
blanched · · focus · HN ↗
(And please note that I do not mean to imply that there are no challenges in manual labor or that software engineering is more important.)