My GitHub years

I worked at GitHub from 2013 to 2026. These 53 posts describe how it worked while I was there, so GitHub may do things differently today. Start with what to read before starting or interviewing at GitHub.

2026 (1 post)

Thirteen years remote at GitHub: what works

6 min read

When I joined GitHub in 2013, I found a company that had rethought how work happens. Thirteen years later, those lessons still shape how I work.

2023 (3 posts)

How to write a great extended leave document

5 min read

A battle-tested template for handing off your responsibilities before extended leave, so your team stays unblocked and nothing falls through the cracks.

Manage like an engineer

8 min read

If issues, pull requests, and project boards are the best way to develop software, should they not also be the best way to manage software development?

2022 (2 posts)

Leaders show their work

10 min read

Great leaders don't just communicate decisions. They explain how and why. Without that context, every decision sounds like "because I said so."

2021 (2 posts)

Nine things a technical program manager does

9 min read

What does a technical program manager do? Nine things, from cross-team coordination to risk, by a product manager who helped found GitHub's TPM org.

2020 (9 posts)

Budget for the hidden "internet tax"

9 min read

Trust and safety is a cost of doing business on the internet. If you're building a platform, budget for abuse protection before someone gets hurt.

How I manage 200+ GitHub notifications a day

7 min read

My GitHub notifications setup: read the web inbox in batches, send @mentions to email, filter the rest in Gmail, and unsubscribe from threads often.

Eight tips for working remotely

10 min read

Tools alone won't make remote work succeed. Eight cultural rules for effective async communication, regardless of your industry or role.

User blocking vs. user muting

9 min read

Why GitHub's approach to user blocking diverges from other social networks, and what's different about moderating a code collaboration platform.

2019 (2 posts)

What lawyers can learn from open source

1 min read

How lawyers can adopt the workflows, tools, and philosophies of open source to make their legal practice more remote-friendly.

2018 (1 post)

2017 (4 posts)

2016 (6 posts)

Removing a feature is a feature

7 min read

Features aren't free. Every time you remove one that doesn't serve your core use case, you're adding an implicit feature that does.

Books for geeks

1 min read

A curated reading list for developers who care about more than just code, covering technology, open source culture, and the business of software.

Twelve things a product manager does

10 min read

What does a product manager actually do all day? After six months of note-taking, here are 12 responsibilities from user advocacy to strategic thinking.

2015 (12 posts)

Why everything should have a URL

15 min read

When knowledge lives in people's heads and inboxes, it doesn't scale. Giving decisions and processes URLs makes context discoverable, async, and opt-in.

The Zen of GitHub

3 min read

Call it taste, culture, or zen. Every organization has shared assumptions that guide decisions and resolve ambiguity in pursuit of its mission.

What does your organization optimize for?

4 min read

Every organization is optimized for one thing. A glance at someone's laptop stickers reveals whether yours optimizes for people or process.

2014 (9 posts)

Geeks and suits

7 min read

In government IT, change depends on geeks and suits. Yet despite being in an industry built on communication, they rarely talk.

15 rules for communicating at GitHub

15 min read

How GitHub used issues and chat for async communication: fifteen rules that eliminate the 'you had to be there' problem in corporate workflows.

What is a Government Evangelist?

3 min read

What a GitHub Government Evangelist does: help agencies ship software better and bring Silicon Valley practices to Washington.

Open source, not just software anymore

8 min read

Open source has always been about the right to modify, not contribute. As those workflows spread beyond software, we may need a new word.

2013 (2 posts)

Jekyll: Where content is truly king

2 min read

Choosing Jekyll over a traditional CMS for government.github.com freed us to spend six months iterating on what mattered most: the content.

Friction

5 min read

Friction, the time between wanting to contribute and actually contributing, is the only metric that matters for open source.