chrisfowles

Or even worse, Frankston.

From my perspective, you might be using take-home challenges incorrectly. The purpose for us is to have something that both sides are now somewhat familiar with, on which to base a technical conversation and ask questions. The actual solution delivered is a small part of the overall value.

Sandbox constraints. Windowing. Browser compatibility issues. Plugins and Integration compatibility.

So you're of the opinion that people who engage in voluntary activities for personal pleasure that put a higher burden on the health system, that those who are more wise about their choices have to use, should not have to pay thier way?

Or are you of the opinion that someone should be denied emergency medical care because they had some sodas on the regular?

Just need to put it in a big bag of rice.

I might agree with buying, it's pretty damaging with selling though.

Because it's unique to the use case, complex, and nuanced. It has to be exactly correct, and it has potentially serious ramifications if the answers are incorrect, potentially with legal ramifications that I'm keenly waiting to see the first cases of.

He's parked in the wrong bay for that charger

Why on earth is your state in git? The tool has built-in functionality to handle just these kinds of workflows. This reads a lot like hitting your thumb with the hammer and blaming hammers.

One of the reasons that English has been so successful as a global business language is its ability to be flexible and splodgable and still make sense.

Anything that avoids ambiguity here is beneficial. Even if the comment itself is perfectly crafted, the potential for misunderstanding remains. This method outlines the expectations for responses much more than it conveys the tone of the message. This is critical information that is often overlooked in asynchronous communication.