> You can optimize for revenue/agony instead. That's a great way to put it. I'm going to start using that one. Tangent: I'm a programmer at a small company, w

> You can optimize for revenue/agony instead. That's a great way to put it. I'm going to start using that one. Tangent: I'm a programmer at a small company, which has three programmers total. I make a decent wage, but one that's significantly smaller than I could make at a larger company. I often get questions from people who can't believe that I'm not jumping at these other opportunities, but I make nearly six figures, my team and bosses trust me, I have nearly unlimited flexibility to choose what I work on and shape my software the way I feel is best, and I get to work full remote and basically make my own hours, giving me all the time I want with my family. It would take an incredible raise to give this up just for better pay. An agony-per-dollar ratio is a perfect way to frame the calculation, and it factors into so many places in life. Many forget that it's not just optimizing for the most revenue possible, but a balance of maximizing revenue and quality of life, and often getting diminishing returns when pushing hard on the former.