Thirteen years remote at GitHub: what works
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.
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.
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.
Most meetings are just information downloads that could've been a doc. Treat them as an escalation based on complexity, not the default starting point.
A battle-tested template for handing off your responsibilities before extended leave, so your team stays unblocked and nothing falls through the cracks.
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?
Seven core responsibilities that define the corporate Chief of Staff role, from tactical office management to strategic advising.
Great leaders don't just communicate decisions. They explain how and why. Without that context, every decision sounds like "because I said so."
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.
Reflecting on eight years at GitHub, from GeoJSON rendering and GitHub Pages to trust and safety, open source licensing, and 200,000 words of blogging.
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.
My GitHub notifications setup: read the web inbox in batches, send @mentions to email, filter the rest in Gmail, and unsubscribe from threads often.
How I choose communication tools at GitHub, from issues to Slack and Zoom, and why the tool you pick matters as much as what you say.
Never force a human to do what a computer can. How to automate code review, issue triage, and maintainer workflows to scale your open source community.
Seven practical ways to set contributors up for success before they open their first issue, from the contributor funnel to being responsive.
Tools alone won't make remote work succeed. Eight cultural rules for effective async communication, regardless of your industry or role.
Why GitHub's approach to user blocking diverges from other social networks, and what's different about moderating a code collaboration platform.
What GitHub's Community and Safety team learned building a trust and safety framework to help maintainers grow healthy, open source communities.
Four resolutions for being a better open source community member, from reducing your bus factor to being a gracious dinner party host to your contributors.
My OSCON 2019 talk on GitHub's approach to empowering maintainers to grow safe, welcoming open source communities that scale alongside the code.
How lawyers can adopt the workflows, tools, and philosophies of open source to make their legal practice more remote-friendly.
CLAs create a hostile developer experience, require significant overhead, and are usually unnecessary given modern open source norms.
There's lots of internet lore around open source licensing. An attorney and open source developer answers the most common questions.
Publishing code isn't enough. Twelve practical tips to attract users, welcome contributors, and grow a healthy open source community.
The best developers don't just write code. They over-communicate, ship the smallest delta, and optimize for users over maintainability.
Small gestures like recognizing birthdays, work anniversaries, and life milestones go a long way, especially when there's no water cooler.
Tips I shared with every new GitHubber, from shipping something in your first two weeks to pushing through the inevitable overwhelm.
Seven traits I've observed in successful GitHubbers over the years, from shipping early and often to the appreciation economy.
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.
A curated reading list for developers who care about more than just code, covering technology, open source culture, and the business of software.
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.
Stop optimizing for power users and edge cases. The real challenge is nailing the out-of-box experience for 80% of users.
Not all pull requests are equal. Six distinct strategies for using pull requests on GitHub, from quick heads-ups to deep reviews.
The best collaboration tools share four traits: open, linkable, asynchronous, and process-capturing. Are you working the way you'd like?
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.
Instead of relying on editors to catch marketing speak, use automated tests and CI to enforce voice, tone, and style guidelines on your corporate blog.
Call it taste, culture, or zen. Every organization has shared assumptions that guide decisions and resolve ambiguity in pursuit of its mission.
Your users don't care how excited you are about your new feature. Twelve rules for writing corporate blog posts that sound human.
A step-by-step guide to creating a branded, customizable developer portal for your organization's open source projects using GitHub Pages and Jekyll.
Publishing code isn't enough. Open source means building communities. Five best practices for engaging contributors and growing your project.
You can't foster open source publicly while running a closed-source culture internally. Five best practices for internal collaboration.
Word Diff automatically converts Word documents to Markdown when you commit to GitHub, so they can be diffed, versioned, and collaborated on like code.
Every organization is optimized for one thing. A glance at someone's laptop stickers reveals whether yours optimizes for people or process.
14 open source apps I built to help non-technical users collaborate on GitHub, from Word-to-Markdown conversion to simplified issue forms.
In government IT, change depends on geeks and suits. Yet despite being in an industry built on communication, they rarely talk.
How GitHub used issues and chat for async communication: fifteen rules that eliminate the 'you had to be there' problem in corporate workflows.
What a GitHub Government Evangelist does: help agencies ship software better and bring Silicon Valley practices to Washington.
Eight reasons government contractors should embrace open source, from free advertising and better code to attracting top talent.
Every decision deserves its own URL, one that captures what was decided, who made the call, and why. Give your content a permanent home.
Publishing code without fostering community is disclosed source, not open source. True open source is a two-way relationship.
Three lessons from moving from the federal government to GitHub: trust, happiness, and treating relationships as assets.
FedRAMP was supposed to make cloud adoption easier for federal agencies. Instead, it's making it harder to keep pace with the private sector.
Open source has always been about the right to modify, not contribute. As those workflows spread beyond software, we may need a new word.
Choosing Jekyll over a traditional CMS for government.github.com freed us to spend six months iterating on what mattered most: the content.
Friction, the time between wanting to contribute and actually contributing, is the only metric that matters for open source.