The “I don’t like what they’re saying, so they shouldn’t be allowed to say it” approach to crisis management
January 8, 2024
Cathedral vs Bazaar People Management
December 8, 2023
How to communicate like a GitHub engineer
October 4, 2023
Transparent collaboration is the andon of your knowledge production system
August 30, 2023
Remote work requires communicating more, less frequently
August 4, 2023
Pull requests are a form of documentation
May 19, 2023
Practice inclusive scheduling
May 19, 2023
Meetings are a point of escalation, not the starting point of a conversation
April 20, 2023
Intro to GitHub for non-technical roles
March 2, 2023
How to write a great extended leave document
January 13, 2023
Manage like an engineer
January 10, 2023
Helpful 404s for Jekyll (and GitHub Pages)
June 30, 2022
Why you should work asynchronously
March 17, 2022
The seven things a corporate Chief of Staff does
March 9, 2022
Leaders show their work
February 16, 2022
Using GitHub Actions to get notified when an API response (or web page) changes
December 15, 2021
How I re-over-engineered my home network for privacy and security
September 1, 2021
Advice for managing open source communities at scale
June 15, 2021
Moderating open source conversations to keep them productive
June 15, 2021
Five (and a half) practical tips for governing your open source project
June 14, 2021
Nine things a (technical) program manager does
March 26, 2021
Octoversary - eight years of optimizing for developer happiness
March 4, 2021
What to read before starting (or interviewing) at GitHub
February 1, 2021
Analysis of federal .gov domains, pre-Biden edition
January 11, 2021
How I over-engineered my home network for privacy and security
December 4, 2020
The top 10 posts of the past 10 years
September 12, 2020
Budget for the hidden “internet tax”
August 31, 2020
How I manage GitHub notifications
August 25, 2020
Tools of the trade: How I communicate at GitHub (and why)
August 14, 2020
Automate common open source community management tasks
August 10, 2020
Seven ways to set open source contributors up for success
May 15, 2020
Eight tips for working remotely
March 18, 2020
User blocking vs. user muting
February 6, 2020
10 lessons learned fostering a community of communities at GitHub
January 17, 2020
Resolutions for sustaining and growing open source communities
January 2, 2020
A community of communities: Empowering maintainers to grow communities around their code
July 18, 2019
Go near, go far, meet in the middle
June 28, 2019
What lawyers can learn from open source
February 6, 2019
Problems, not solutions
July 16, 2018
Yes, No, Maybe
May 4, 2018
Why you probably shouldn’t add a CLA to your open source project
January 2, 2018
Everything an open source maintainer might need to know about open source licensing
November 28, 2017
Twelve tips for growing communities around your open source project
November 10, 2017
How not to prioritize a feature
June 19, 2017
Seven ways to consistently ship great features
May 23, 2017
Your project’s README is your project’s constitution
April 14, 2017
Using protected branches to empower non-code contributors on GitHub
April 14, 2017
Three easy ways to show employees they’re appreciated
April 4, 2017
Bikeshed honeypots
March 1, 2017
How I Atom (for prose)
December 23, 2016
Eight things I wish I knew my first week at GitHub
October 31, 2016
The seven habits of highly effective GitHubbers
September 13, 2016
How to make a product great
August 22, 2016
Why you shouldn’t write your own open source license
August 1, 2016
Removing a feature is a feature
July 21, 2016
Books for geeks
July 11, 2016
Twelve things a product manager does
June 6, 2016
Moderating a controversial pull request
May 11, 2016
The missed opportunity that is the White House Open Source Policy
April 11, 2016
Optimizing for power users and edge cases is the easy part
March 8, 2016
How to derail any meeting
January 15, 2016
The six types of pull requests you see on GitHub
December 8, 2015
Open source as Yelp for software
December 8, 2015
Why open source
November 23, 2015
Four characteristics of modern collaboration tools
November 18, 2015
Why everything should have a URL
November 12, 2015
The three biggest challenges in government IT
October 18, 2015
Bringing open source workflows to the enterprise
September 21, 2015
How to add an “improve this content” button to your GitHub Pages site
September 13, 2015
How GitHub uses automated testing to empower developers to write less-corporate blog posts
September 10, 2015
Five principles to guide any government IT effort
August 23, 2015
The Zen of GitHub
August 12, 2015
Speak like a human: 12 ways tech companies can write less-corporate blog posts
July 20, 2015
Open procurement: procurement in an increasingly open source world
July 11, 2015
Merge by committee
June 22, 2015
Using GitHub Pages to showcase your organization’s open source efforts
June 11, 2015
Copyright notices for open source projects
June 3, 2015
Test your content
May 22, 2015
Analysis of federal .gov domains, 2015 edition
May 11, 2015
Eight lessons learned hacking on GitHub Pages for six months
April 27, 2015
The difference between 18F and USDS
April 22, 2015
19 reasons why technologists don’t want to work at your government agency
April 21, 2015
Five best practices in open source: external engagement
March 17, 2015
Five best practices in open source: internal collaboration
March 8, 2015
Explain like I’m five: Jekyll collections
February 20, 2015
Why your agency’s first open source project is going to be a flop
February 11, 2015
Diff (and collaborate on) Microsoft Word documents using GitHub
February 6, 2015
What does your organization optimize for?
January 27, 2015
The fine print nobody reads: what to do so government can use your service
January 26, 2015
Hacking GitHub: 14 simple tools to help introduce open source to the uninitiated
January 11, 2015
Why you should care about HTTPS, even if you have nothing to hide
January 6, 2015
Geeks and suits
December 18, 2014
The myth of government IT
December 17, 2014
A White House open source policy written by a geek
November 24, 2014
15 rules for communicating at GitHub
November 6, 2014
What is a Government Evangelist?
October 15, 2014
What’s next for federal IT policy, IMHO
October 15, 2014
Eight reasons why government contractors should embrace open source software
October 8, 2014
Everything a government attorney needs to know about open source software licensing
October 8, 2014
If you liked it then you should have put a URL on it
October 7, 2014
Disclosed source is not the same as open source
September 29, 2014
Our code deserves better
September 29, 2014
Open source is (not) insecure
September 22, 2014
Three things you learn going from the most bureaucratic organization in the world to the least
August 24, 2014
Why isn’t all government software open source?
August 3, 2014
Why FedRAMP actually makes it harder for government agencies to move to the cloud
July 29, 2014
Analysis of Federal Executive .govs (Part Deux)
July 7, 2014
How to identify a strong open source project
June 2, 2014
Open government is so ‘08, or why collaborative government is the next big thing
June 2, 2014
Word versus Markdown: more than mere semantics
March 31, 2014
Want to innovate government? Focus on culture
March 21, 2014
Header hover anchor links on GitHub Pages using Jekyll
March 13, 2014
Open source, not just software anymore
January 27, 2014
Why no one uses your government data
December 30, 2013
That’s not how the internet works
November 21, 2013
Jekyll: Where content is truly king
October 30, 2013
Ten Things You Learn As A Presidential Innovation Fellow
September 30, 2013
Treat Data As Code
September 16, 2013
Friction
August 11, 2013
Everyone Contributes
August 11, 2013
Bet on the little guy
July 2, 2013
The technology’s the easy part
July 1, 2013
How to convert Shapefiles to GeoJSON maps for use on GitHub (and why you should)
June 26, 2013
An open letter to government CIOs
June 12, 2013
We’ve Been Selling Open Source Wrong
May 14, 2013
The store that sells only one thing.
February 27, 2013
The next big thing is already here
February 6, 2013
What is a ‘Hacker’?
February 4, 2013
Securing the Status Quo
December 26, 2012
Deprecate Management
December 16, 2012
Why WordPress’s next version should just give it a REST already
December 15, 2012
We’ve been trained to make paper
October 19, 2012
Open Source is not a verb
October 15, 2012
Welcome to the Post-CMS World
October 1, 2012
Government’s Release of Federally Funded Source Code: Public Domain or Open Source? Yes.
July 26, 2012
The Demise of the Personal Dashboard
July 10, 2012
Why You Should Always Write Software as Open Source, Even When It’s Never Going to Be
June 26, 2012
Publishing Government Data That Developers Will Actually Use
June 2, 2012
WordPress as a Collaboration Platform
May 8, 2012
Enterprise Open Source Usage Is Up, But Challenges Remain
April 23, 2012
CFPB Accepts First Citizen-Submitted Code on Behalf of Federal Government
April 15, 2012
What’s Missing from CFPB’s Awesome New Source Code Policy
April 10, 2012
WordPress for Government - A Problem of Perception
March 5, 2012
PHP is Insecure (and Other Enterprise Open-Source F.U.D.)
March 2, 2012
GitHub for Journalism — What WordPress Post Forking could do to Editorial Workflows
February 28, 2012
Open-Source Alternatives to Proprietary Enterprise Software
February 27, 2012
Towards a More Agile Government
November 29, 2011
Federal Agility: a Cultural Solution to a Technical Problem
November 1, 2011
Why Digital Talent Doesn’t Want To Work At Your Company
October 29, 2011
Advanced Workflow Management Tools for WP Document Revisions
October 24, 2011
Analysis of Federal Executive .govs
September 7, 2011
Why WordPress
September 1, 2011
Enterprise, Open Source, and Why Better is not Enough
August 31, 2011
WP Document Revisions — Document Management and Version Control for WordPress
August 29, 2011
When all you have is a pair of bolt cutters…
April 4, 2011