Technology, software, startups, travel, and leadership advice from GitHub’s COO.
At early GitHub, prioritization wasn’t just important: it was critical to scaling adoption and focusing on what was going to help the biggest number of developers. Inspired a bit by the RFC keywords, I boiled down prioritization into three categories: MUST, SHOULD, and COULD.
This week, I'm reflecting on a post I wrote in May 2013 after one month of working at GitHub. This past Monday marked my first month at GitHub. It’s been an amazing experience. Instead of writing a long post, I’m going to try to
The easiest and best options for international cell phone data while traveling internationally.
When working on big complicated projects, I found myself first wanting to take some time for myself to strategize, consolidate my thinking, and in some ways build an energy reserve. Since then, I've made personal retreats a regular tool in my toolbox.
We spend so much of our lives telling ourselves who we are going to be. We read the blogs of influential people, go to conferences to see them speak, and tell ourselves “if I just conquer this one thing I could be just like them”.
Josh Long wrote an article describing how to kill your heroes: go out there and do something worthwhile and stop regaling your heroes for the ability to ship. Tom Preston-Werner gave us a great example of what it means to ship with TOML.