I'm and

Not that there's much insightful there worth preserving, but if you're looking for my Tweets, you can find them archived at regardless of what happens to this site.

Remote work requires communicating more, less frequently, because async communication involves less frequent, but richer communication. There is less talking about the work and more doing it, allowing the system to optimize for throughput and flow.

Shoutout to the commenter on the thread who called me an intern and unknowingly created an inside joke / troll that continues to this day.

Also, the comments on the orange site are exactly what you'd expect. Amazing to see how developer centric we were, even back then, and how much feedback from that thread was implemented in the following weeks.

Exactly 10 years ago today, I 🚢'd my first GitHub feature, GeoJSON rendering. The base layer has since moved from MapBox to Azure Maps, but the feature is still rendering more than 7 million maps a year across more than 27 million .geojson files.

Practice inclusive scheduling. When working as a distributed team, be mindful of cultural differences, time zones, encouraging breaks between meetings, and connecting as humans.

Pull requests are a form of documentation. When authoring a PR, use the body as an opportunity to document the proposed change, especially the “why”, and cross link any related issues or other PRs to create a trail of breadcrumbs for future contributors.

If you're a Google Workspace user and are interested in pulling your own stats (calendar + email), I wrote a thing:

I made a few updates to my "Intro to GitHub for non-technical roles" article. Glad it has been helpful. Please keep the questions and feedback coming.

If you’re at a large(r) tech company that you joined when it was closer to a start up, what aspects of your organization’s culture or values do you wish you could purposefully preserve (or bring back)?.

GitHub isn’t just for software developers. If you work with or alongside software development teams, this brief guide includes everything that you need to know to get started confidently with GitHub.

I’ve given the “life as a Hubber” onboarding talk for a year+ now. Each time I tell the story about how I adopted the “conjunction” y’all as a gender neutral reference to a group. 100s of Hubbers onboarded and not a single one pointed out that “y’all” is actually a contraction.😂.

Fish sticks are really having their moment.

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? . Make work visible. Write things down. Embrace collaboration. Manage like an engineer.

Is there a good solution for ad/tracker blocking on mobile (for browser AND apps)? I use AdGuard at home (, but I have different reasons for not trusting the two popular DNS filtering services, and running a wireguard split VPN eats 30%+ battery on iOS. 🤷‍♂️.

RT @lukehefson: While interviewing, a number of companies have been interested in my QA/QE/quality team experience – especially since I swi….

If you work in or around a large organization, I can’t recommend @MarinaNitze and @NickSinai’s new book, “Hack Your Bureaucracy” enough. Just finished, and it’s the bureaucratic decoder ring for “getting things done” I wish I had when starting my career.

Today marks exactly one year for me as Chief of Staff for GitHub's Security team. To honor the occasion, I wrote a brief overview of how we use GitHub to secure GitHub, relying on Issues, Projects, and Actions, to power our planning and tracking organizational “operating system”.

If you maintain a Jekyll site, I wrote up a brief tutorial on how to use the Jekyll Sitemap plugin and a few lines of JavaScript to automatically have your 404 – not found page suggest similar (valid) URLs to the one requested.