gfunk911
Joined 18 years ago
Joined 18 years ago
My ideal would be to try changing 2s and 3s to 3s and 4s. But that will never happen.
Every league does this of course, NBA did it just last year with the stealth rule changes around fouls.
This is why we built merge queue. We’ve reduced the tension between branch stability and velocity. Merge queue takes care of making sure your pull request is compatible with other changes ahead of it and alerting you if something goes wrong. The result: your team can focus on the good stuff—write, submit, and commit. No tool sprawls here. This flow is still in the same place with the enablement of a modified merge button because GitHub remains your one-stop-shop for an integrated, enterprise-ready platform with the industry’s best collaboration tools.
The obvious result (to everyone but the creators of the rule I guess) is that, if a game is tied near the end of regulation, it is best for both sides if the game goes to overtime. There are 2 points available for a game decided in regulation, but 3 if decided in overtime. I assume both teams would sit quietly and wait for overtime if it were tolerated.
It seems possible that Palin lost due to voters incorrectly expressing their preferences by not putting a 2nd choice. If that is a routine thing, then it is indeed a problem with ranked choice voting in the real world, but it is NOT a structural flaw as you are claiming.
https://www.techopedia.com/definition/2239/cpu-lock
It’s cheaper to physically put the functionality in all the cars than to differentiate at assembly time. We don’t have the same visceral reaction to paying for options at the dealer.
(I am assuming they aren’t adding this charge RETROACTIVELY. That’s very different)
There's a big difference between "code being in one file" and "code being in one function." It sounds like the OP had something reasonably close to "one function," whereas the HN code has a lot of (what appear to be) small well designed methods.
# Retries a command a with backoff.
#
# The retry count is given by ATTEMPTS (default 100), the
# initial backoff timeout is given by TIMEOUT in seconds
# (default 5.)
#
# Successive backoffs increase the timeout by ~33%.
#
# Beware of set -e killing your whole script!
function try_till_success {
local max_attempts=${ATTEMPTS-100}
local timeout=${TIMEOUT-5}
local attempt=0
local exitCode=0
while [[ $attempt < $max_attempts ]]
do
"$@"
exitCode=$?
if [[ $exitCode == 0 ]]
then
break
fi
echo "Failure! Retrying in $timeout.." 1>&2
sleep $timeout
attempt=$(( attempt + 1 ))
timeout=$(( timeout * 40 / 30 ))
done
if [[ $exitCode != 0 ]]
then
echo "You've failed me for the last time! ($@)" 1>&2
fi
return $exitCode
}