‹ BackHN Continuity

Thread

Mario Meets Pareto

742 points · 136 comments · theanonymousone

  1. Agentlien · · focus · HN ↗
    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.

    1. Georgelemental · · focus · HN ↗
      Well then, you would prioritize "fulfilling" in your utility function. Others might make a different choice; e.g. a single parent who needs to save time and energy for family might prefer "easy" at the cost of boring drudgery
      1. Agentlien · · focus · HN ↗
        I think what I am saying is more that "easy" is too broad a vector to optimize along because it combines too much - both good and bad. I don't want a job without challenges of any kind.

        But I definitely want a job without stress, danger, or physical strain on my body. Perhaps I am just looking for a similar word which doesn't imply anything about the complexity of the task at hand.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.