はてなブックマーク

A month after launching, GitHub hosted one thousand repositories. Three years later, we host over three million. In the same time we’ve gone from one thousand users to over a million. This type of scaling presents some interesting technical challenges. I’ll dig into our development workflow and how we address concepts like scaling, deployment, code review, and testing. It also presents some intere

Currently / Founder of Signed and Calendearing. Invested in hundreds of startups via Tifo. Previously / Second engineer hired at GitHub, and advised GitLab ahead of their IPO. Yesterday Penelope Trunk wrote a guest post on TechCrunch that told us all to “Stop Telling Women To Do Startups”. Pardon me while I do just the opposite. Startups don’t need to suck Trunk’s article has a lot of arguments th

Guy walks into a bar. Bartender glances at his shirt, which proudly proclaimed “INTRAMURAL FIELD HOCKEY CHAMPIONS 2002”. Bartender comments: “You know, that shirt reminds me of a story I once heard. “A team of researchers ended up shipwrecking their oceanliner on a beach. Fearing death, they built shelters and huddled together for warmth. One researcher, fed up with another’s statement that increa

Build features fast. Ship them. That’s what we try to do at GitHub. Our process is the anti-process: what’s the minimum overhead we can put up with to keep our code quality high, all while building features as quickly as possible? It’s not just features, either: faster development means happier developers. Slides Video References Merlin Mann’s “Mud Rooms, Red Letters, and Real Priorities” sinatra_

Currently / Founder of Signed and Calendearing. Invested in hundreds of startups via Tifo. Previously / Second engineer hired at GitHub, and advised GitLab ahead of their IPO. The problem with shit work is that no one likes doing it, but an awful lot of people say they do. Shit work Take a look at Twitter Lists. The idea behind Twitter Lists was that users would carefully cultivate lists on Twitte

I'm on Threads, Bluesky, and unfortunately Twitter. You can also find me on GitHub.

GitHub has been pretty public about how we work. We love to write about it, tweet about it, and give talks about it. But there’s usually a lingering question of whether this type of workflow scales. It does. It scales. We do things differently at GitHub: we work out of chat rooms, we don’t enforce hours, and we have zero managers. People work on what they want to work on. Product development is dr

You're reading part three of How GitHub Works, a three-post journey into how we work at GitHub. They're all separate posts on different topics, but if you're interested you can also read the other two: Hours are Bullshit and Be Asynchronous. We want to foster a creative environment. We love it when employees hack on side projects. It gets people excited. Excitement is contagious, and spreads easil

You're reading part two of How GitHub Works, a three-post journey into how we work at GitHub. They're all separate posts on different topics, but if you're interested you can also read the other two: Hours are Bullshit and Creativity is Important. This is — by far — my favorite aspect of working at GitHub. Everything is asynchronous. Chat GitHub didn’t have an office for the first two years. Chat

You're reading part one of How GitHub Works, a three-post journey into how we work at GitHub. They're all separate posts on different topics, but if you're interested you can also read the other two: Be Asynchronous and Creativity is Important. Frederick Winslow Taylor wrote the seminal analysis of management and efficiency in 1911 with The Principles of Scientific Management. He took the first sc

Currently / Founder of Signed and Calendearing. Invested in hundreds of startups via Tifo. Previously / Second engineer hired at GitHub, and advised GitLab ahead of their IPO. I love Apple. I love Apple so much that if someone gave me a bulletproof vest made out of MacBook Airs, I’d strap it to my back and take a bullet to my chest to protect my precious aluminum friends. But Steve’s lying to us w

Documentation is the single most important change I’ve made to my coding style in the last year. Documentation is Personal I’m not talking about injecting a few comments in front of confusing lines here and there. I’m talking about taking a firm, consistent view at how you document your methods, your classes, and your projects, and then sticking to that mentality. Documentation is mostly described

I build, advise and invest in startups. I'm currently the cofounder of WorkOn and invest at Tifo. Previously, I was one of the first engineers at GitHub, and have advised companies like GitLab.