Ben Balter

Director of Engineering Operations & Culture @GitHub. Previously @GitHub Security, @GitHub Trust & Safety, @pifgov.

[Ben Balter @benbalter]

I'm https://t.co/Mgo1Kf3gZ4, https://t.co/CHBkCNRxb0, and https://t.co/CzuwWz3wcz.

[Ben Balter @benbalter]

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

[Ben Balter @benbalter]

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. https://t.co/R3J5pCjUho

[Ben Balter @benbalter]

@muanchiou @github Not my remit anymore, but if you shoot me an email with details ([email protected]), happy to ask around on your behalf.

[Ben Balter @benbalter]

Shoutout to the commenter on the thread who called me an intern and unknowingly created an inside joke / troll that continues to this day. https://t.co/2XNnkmFX9K

[Ben Balter @benbalter]

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. https://t.co/1NiPrgsW0o

[Ben Balter @benbalter]

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. https://t.co/CG6VTjfyhx

[Ben Balter @benbalter]

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

[Ben Balter @benbalter]

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. https://t.co/RrmuMZgR3A

[Ben Balter @benbalter]

@BryanHirsch I used to do this, but with coffee. The last hour of every Friday was blocked off for “strategic planning” which meant the week ahead + other important, but not urgent stuff.

[Ben Balter @benbalter]

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

[Ben Balter @benbalter]

@corywilkerson There’s another way?

[Ben Balter @benbalter]

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. https://t.co/rG4RW6Xgnh

[Ben Balter @benbalter]

@PhaniRa08905617 @JasonEtco I had forgotten about this!

[Ben Balter @benbalter]

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)?

[Ben Balter @benbalter]

@JasonEtco I _still_ remember the first demo of Atom I saw in 2013. I thought it was sci-fi.

[Ben Balter @benbalter]

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. https://t.co/rG4RW6Xgnh

[Ben Balter @benbalter]

@holman @danishkhan A quick Bing search suggests https://t.co/zlN1ZdeIny or https://t.co/Gtj1QWrSs2 _might_ be that?

[Ben Balter @benbalter]

@chacon @haacked Books by the foot!