jbarnette | 6 years ago | on: Scientist: A Ruby library for carefully refactoring critical paths
jbarnette's comments
jbarnette | 7 years ago | on: Remembering Evi Nemeth, the “Matriarch of System Administration”
jbarnette | 8 years ago | on: Kubernetes at GitHub
jbarnette | 12 years ago | on: State of the Octoverse 2013
jbarnette | 12 years ago | on: State of the Octoverse 2013
jbarnette | 12 years ago | on: Google Analytics for GitHub
jbarnette | 12 years ago | on: How GitHub No Longer Works
Added: That's a little too glib, sorry. Let me try again: From my perspective, if there's something that needs to be done at GitHub there are a few possibilities:
1. It needs to be done and it's getting done,
2. It needs to be done and it's not getting done, or
3. It's bullshit.
Cases of #3 become obvious pretty quickly. The best evidence: Searching for ways to make someone do it because nobody stepped up.
Cases of #2 can happen for a bunch of different reasons, but malice, apathy, laziness, or incompetence are the least likely ones. The most likely: Not enough hours in the day or not enough people with the knowledge necessary to be worried. No matter the reason for #2, someone at GitHub who is worried will generally try to get others to share their priorities, by persuasion, by hiring, or by prototyping.
Or occasionally by just jumping up and down and wailing.
jbarnette | 12 years ago | on: How GitHub No Longer Works
jbarnette | 12 years ago | on: Identicons
jbarnette | 12 years ago | on: More Git and GitHub Secrets
jbarnette | 12 years ago | on: GitHub's on your phone
jbarnette | 13 years ago | on: Free private Github repos for students and edu people
jbarnette | 13 years ago | on: Free private Github repos for students and edu people
jbarnette | 13 years ago | on: Github turns five
jbarnette | 13 years ago | on: Github turns five
jbarnette | 13 years ago | on: STL File Viewing
jbarnette | 13 years ago | on: Introducing Boxen
jbarnette | 13 years ago | on: Introducing Boxen
jbarnette | 13 years ago | on: Ruby inline assembler
jbarnette | 13 years ago | on: Introducing Contributions
"Let's pretend you're changing the way you handle permissions in a large web app. Tests can help guide your refactoring, but you really want to compare the current and refactored behaviors under load."