nottathrowaway3

It evokes a larger brand of similar wordplay which is basically the professional equivalent of "it's not you, it's me". The reason people don't like it is that it essentially tries to trick applicants into misunderstanding their economic interest, rather than just admit they're rejecting you because you're bad.

> If such an applicant gets a job...

Getting the job offer would not cause any of those problems. By getting it you would build valuable interviewing experience. Taking it is the thing that's not in your interest. That's all I'm trying to say.

> I have the conclusion opt-in async/await is a mistake. I think high level language/runtime like c# should handle it automatically...

This is not a good idea unless you like having to make all your code thread-safe (well, async-safe). Explicit declaration of "hey this method might not run all at once or be interleaved with other methods" is a good idea; explicit opt-in is the same in every other implementation of async/await (ex: js).

tl;dr

> language and compiler capable of rewriting normal control flow into a state machine implementation of coroutines

The median chess player is usually described as mediocre (if you ask chess players). They suck as badly as the median clarinet player in your high school band/orchestra.

> "and no one will ever help you in life" ... strange thing to say in a hospital bed?

It's strange until you get the hospital bill in the mail.

> I try to click less on negative stories and more on positive stories.

An alternative approach is to consume news from multiple countries (including your own). It's so interesting to see how all the fnords are different and just how conditioned you were to consume the one kind of media designed for your country.

The answer will either be some socialist rationing policy, or genocide.

Current "work for a living" systems only sustained the population because a human could be the most cost-effective way to get something done. Unless there are still tasks where human labor is the best option (research jobs maybe), this entire economic system will collapse.

> then it's in the best interest of ... the applicant that they not be hired

This kind of wordplay makes sense from HR's perspective. Ex: it "wouldn't be a fit for you anyway", there are "other jobs where you'll be able to grow more", etc.

The best interest of the applicant is always to get an offer (or stop the interview process of their own volition). Not get rejected by a screen and get zero feedback. Obviously this costs more for the business, which is why they have incentive to use that kind of reasoning.

Even if you shouldn't take it, competing offers can be used in various negotiations. And getting practice at interviewing is how you get better at interviewing (and at your actual job).

Depends if it was a standard project format like npm or setup.py.

The risk is, by asking, you indicate you don't know how to use standard industry tooling.

"hey, your starter code is not running in my environment, have any documentation about how to set it up" is a better question to ask when it's some custom script they hacked together.