- How to communicate like a GitHub engineer (with Allison Matlack)
- Transparent collaboration is the andon of your knowledge production system
- Remote work requires communicating more, less frequently
- Practice inclusive scheduling
- 15 rules for communicating at GitHub
- The seven habits of highly effective GitHubbers
- Why everything should have a URL
Ben Balter is the Director of Hubber Enablement at GitHub, the world's largest software development platform. In this role, he drives employee engagement, productivity, and organizational health for GitHub's distributed workforce through continuous learning (with a focus on AI fluency), async communication patterns optimized for remote-first teams, company events, and AI-driven automation of business processes. Previously, as Director of Engineering Operations and Culture, Ben led a team supporting engineering executives, fostering diversity and inclusion, and improving operational excellence. Earlier in his GitHub tenure, he served as Chief of Staff for Security, Staff Technical Program Manager for Enterprise and Compliance, Senior Product Manager for Trust and Safety, and GitHub's Government Evangelist, where he led efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies.












