Googling "personal assistant salary", it looks like the average in the US is ~$50k/year. So a personal assistant would cost more, but it is in the right ballpark where that could be a better choice than that raise if this is the reason for the raise:

> with the skills necessary to do enough of your job that you go from "overworked" to "takes off early most days to go play golf."

Nobody negotiates net. It's not even practical. Your tax situation will depend of the other revenues you might receive on top of your wages and the deductions you are eligible to and your employer doesn't have to know about that.

Which is to say, if you're making USD$100k/yr working for Ericsson in Sweden (where you're in the highest, 52.9%, tax bracket for any marginal income above USD$83k), they're gonna be thinking differently about how to reward you as a high performer, vs if you were making USD$100k/yr at Google in the US (where that salary would instead just have you scraping the top of the 22% tax bracket.)

Google would almost certainly just give you more money — and would likely continue to do that indefinitely, as even the highest US federal tax bracket (37% at USD$600k/yr) isn't too onerous. Ericsson, on the other hand, might already rather offer you something non-monetary and "cheap" for them (e.g. a company car), rather than biting the bullet on a "substantial, productivity-incentivizing" raise (i.e. one that meaningfully increases your net income.)

And that is why precisely why salaries tend to be lower in many European countries (that have these high tax brackets); and why everyone in those countries instead expects / demands / enshrines requirements in law for tons of non-monetary benefits, like long vacations! "Purely salary" and "salary levels off, then tons of non-material benefits" are both Nash equilibria in compensation space; just very different ones.

To begin with, non monetary benefits have to be declared in most European countries and impact your tax rates and are taxed the same way than giving you more money so your whole dodgy reasoning immediately falls apart.

The less crass answer: In almost every company, you’re being hired on a salary band, so unless you’re at the top of that band in the initial offer there is room to go up, so you can typically push a bit higher. The trick is to make a request that’s higher than what they initially offer but not so high that they outright reject it without additional conversation, and if they are play hardball, and don’t budge on anything, you just reject their offer. It does mean you have to be comfortable rejecting an otherwise decent or good offer, but presumably most companies are willing to negotiate with a good candidate so this shouldn’t be a problem in practice if the negotiation is done in a considered way.

I was an employee so this didn’t apply to me, but for my freelancer friends it seemed very unfair that they had to use private.

When you're very sick you hardly have time, money and energy do deal with a lawsuits so that you can get the care you desperately need. By the time you win your lawsuit you could be dead or your condition worse from the stress.

This program will run forever, since we never write to stdout, stdout never "drains":

    setInterval(() => console.error("stderr: ", new Date().toISOString()), 5_000)
    process.stdout.once("drain", () => {
      console.error("stderr: stdout.once.drain, exit")
      process.exit(0)
    })

Note this is ignoring anything about the reader, for which Racket has substantially more powerful functionality around than Clojure.