Reorgs happen
In thirteen years at GitHub I was part of 25 reorgs—almost one every six months. Reorgs are a constant in tech, not a crisis. Here's how to navigate them.
In thirteen years at GitHub I was part of 25 reorgs—almost one every six months. Reorgs are a constant in tech, not a crisis. Here's how to navigate them.
Most 1:1s waste your team's only protected synchronous time on status updates. Here's how to run ones worth showing up for.
Why you need a running record of your wins—and how to keep one without dying of embarrassment
GitHub isn't just for developers. A practical guide for non-technical roles to follow along, collaborate, and track work with confidence.
How GitHub uses issues and chat for async communication — fifteen rules that eliminate the 'you had to be there' problem in corporate workflows.
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?
Great leaders don't just communicate decisions—they explain how and why. Without that context, every decision sounds like "because I said so."
Async is what makes remote work actually work. It produces better outcomes, improves work-life balance, and unlocks flow beyond Cold War-era workflows.
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.
Coming July 21, 2026
Open&Async
The collaborative software development playbook for remote and distributed teams. Drawing on a decade at GitHub — sign up to get notified when it launches.
Get notifiedIn an office, some of your visibility is free. Go remote and it drops to zero. Working loudly makes your impact visible as you do it—not after the fact in a status update nobody reads.
AI-augmented program management is the natural evolution of async-first and engineering-inspired workflows — amplifying human judgment, not replacing it.
Announcing noagendanomeeting.net — a single-page site advocating that every meeting deserves an agenda, and most meetings deserve to be a document instead.
Like what you read? Subscribe via RSS to get notified when new posts are published.
AI coding agents aren't replacing developers — they're extending the transparency, code review, and collaboration patterns behind open source.
When I joined GitHub in 2013, I found a company that had rethought how work happens. Thirteen years later, those lessons are more relevant than ever.
Set up LanguageTool as a free, open-source Grammarly alternative that runs locally on your Mac. No subscription required.
Silencing dissent erodes trust, invites negativity, and stifles learning. The best leaders embrace transparency instead.
What if we applied open source's cathedral vs. bazaar metaphor to management? Cathedral managers control; bazaar managers empower.
Like Toyota's andon cord, transparent collaboration lets anyone stop the line when they spot a problem in knowledge work.
Async communication is like gzip compression for humans—more upfront processing, but greater throughput with fewer packets.
Pull requests capture not just what changed, but who, why, and what alternatives were considered. Treat every PR as a time capsule for future contributors.
Small scheduling choices — writing dates unambiguously, including time zones, and building in breaks — make distributed teams feel included.
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.
How to build 404 pages for Jekyll and GitHub Pages that automatically suggest similar URLs to those requested, using Levenshtein distance and your sitemap.
Seven core responsibilities that define the corporate Chief of Staff role, from tactical office management to strategic advising.
A customizable GitHub Actions workflow that uses cURL, jq, and Twilio to notify you via text message when a web page or API response changes.
How I used Docker Compose, Ansible, and Caddy to re-over-engineer my network setup for easier maintenance, treating my Raspberry Pi like cattle, not a pet.
A four-part series on managing open source at scale: setting contributors up for success, automating workflows, governance, and moderation.
Keep open source discussions productive with codes of conduct, community reporting, and tiered moderation tools to de-escalate conflict.
Practical tips for governing your growing open source project, from org-owned repos and enforcing 2FA to the triage role and appointing community managers.
What a Technical Program Manager actually does day-to-day, from a Product Manager who found the responsibilities were already familiar.
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.