Linux was remote-first three decades before "remote-first" was a LinkedIn headline.
Open source is the largest distributed-work experiment in history — it just never called itself that. New essay on what everyone else is still catching up to:
allthingsopen.org/articles/o…
3
2
270
Most companies didn't go remote — they digitized the office. Same meetings, same interruptions, now on Zoom.
Open and Async is out today: the open-source way of working — in the open, in writing, async by default — turned into a playbook for your team.
open-and-async.com
The book also ships as software. Its frameworks are an MCP server — decision docs, async standups, sync-vs-async triage, right inside your agent:
claude mcp add open-async -- npx -y @open-and-async/mcp
Source: github.com/open-and-async/mc…
2
1
117
Not that there's much insightful there worth preserving, but if you're looking for my Tweets, you can find them archived at ben.balter.com/tweets/, 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. ben.balter.com/2023/08/04/re…
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. github.blog/2013-06-13-there…
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. news.ycombinator.com/item?id…
1
3
488
Shoutout to the commenter on the thread who called me an intern and unknowingly created an inside joke / troll that continues to this day. news.ycombinator.com/item?id…
Practice inclusive scheduling. When working as a distributed team, be mindful of cultural differences, time zones, encouraging breaks between meetings, and connecting as humans. ben.balter.com/2023/05/19/pr…
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. ben.balter.com/2023/05/19/pu…
If you're a Google Workspace user and are interested in pulling your own stats (calendar + email), I wrote a thing: github.com/benbalter/gmail-a…
1
196
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. ben.balter.com/2023/03/02/gi…
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. ben.balter.com/2023/03/02/gi…
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.😂
2
16
1,837
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.
ben.balter.com/2023/01/10/ma…
Is there a good solution for ad/tracker blocking on mobile (for browser AND apps)? I use AdGuard at home (ben.balter.com/2021/09/01/ho…), 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. 🤷♂️
5


