Recent submissions

Comment · 5 months ago
How much overlap do you feel like dynamic workflows have with RLMs?
Comment · 1 year ago
I love the modern game. I just think the pendulum has swung a tiny bit too far toward 3s in the past 3-4 years, that's all. Just a nudge in the other direction.

My ideal would be to try changing 2s and 3s to 3s and 4s. But that will never happen.

Comment · 1 year ago
The comparison IMO is that how baseball is played changed over time as teams optimized, and some of those changes are undesirable from the perspective of an entertainment product. So MLB changed the rules to increase plays at the margin that are on average considered "more exciting."

Every league does this of course, NBA did it just last year with the stealth rule changes around fouls.

Comment · 1 year ago
One of my favorite ridiculous stats. Bruce Bowen had one year where he shot better from 3 than he did on free throws. He was a dreadful shooter, but somehow he taught himself to be passable at this one specific skill, corner 3s.
Comment · 3 years ago
Collaborative coding is powerful. But to be at your team’s most optimized state, you need automated branch management that enables multiple developers to commit code on a daily basis, without frustration. This can happen if your team’s branch is busy with many team members onboarding the same commit onramp. This can be frustrating for your team, but, more importantly, it gets in the way of shipping velocity. We don’t want that journey for you!

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.

Comment · 3 years ago
In the NHL, you get 2 points for winning, 0 points for losing in regulation, and 1 point for losing in overtime.

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.

Comment · 4 years ago
Do we know for a fact the breakdown of 2nd choices on ballots where Palin was the first choice? If not, you are only speculating.

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.

Comment · 4 years ago
Comment · 4 years ago
This seems no different than Intel manufacturing fewer distinct things and using CPU locking to sell at more price points.

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)

Comment · 4 years ago
This is a good point, but there's also a key difference.

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.

Comment · 4 years ago

  # 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
  }
Comment · 4 years ago
You brilliant lunatic
Comment · 4 years ago
I might love this. Last time I checked on the Actions docs, they seemed to say a lot, while still leaving me confused somehow.
Comment · 4 years ago
Exactly. I find it helps to also state that it doesn't mean "Don't Repeat Characters"
Comment · 4 years ago
Ruby already has group_by, unless I'm misunderstanding what you're saying

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton