The next big thing is already here
Looking for the next big thing? Chances are it’s already here, and chances are the open source community is using it. If you wanted to know the next trend in medicine, it makes sense to look at how doctors take care of themselves. The same is true for geeks. It’s about looking to the early adopters.
Countless technologies we take for granted today, began their lives as staples of the open-source development workflow. Command-line based text editors like VI — essential to the creation of the first open source projects — quickly gave rise to more evolved word processors like WordPerfect and Microsoft Word. Centralized version control, an open-source necessity eventually found itself in the hands of consumers in the form of DropBox, and if the @ reply and #hashtag vernacular of Twitter looks familiar, that’s because it first emerged, nearly identically, as developers first collaborated on IRC.
Each of these technologies, although they got their start in open source, found their way to market in a radically different, often simplified form. This follows a pattern of innovation developing in one market, before being introduced, disruptively, into another.
So what’s next? A lot. For one, we’re seeing a pretty substantial shift among open source developers towards distributed version control. For another, we’re seeing APIs and robust client-libraries shifting application logic to the edge. Last, many open-source projects are crowd sourcing information collection and curation, especially around geospatial data, to name a few examples, but there’s much more out there.
To be sure, not all innovations come from the open source world. Far from it in fact. But as the earliest adopters and arguably those most critical of the tools they use, as a general rule, if the open source community as a whole is backing an effort, there’s a good chance it’s a winner.
h/t Phil Ashlock for the inspiration for this post.
If you enjoyed this post, you might also enjoy:
- Why open source
- 19 reasons why technologists don't want to work at your government agency
- Twelve tips for growing communities around your open source project
- Everything an open source maintainer might need to know about open source licensing
- Open source, not just software anymore
- 15 rules for communicating at GitHub
- Five best practices in open source: external engagement
- Four characteristics of modern collaboration tools
- The difference between 18F and USDS
- Speak like a human: 12 ways tech companies can write less-corporate blog posts
- Why you probably shouldn't add a CLA to your open source project
Ben Balter is the Director of Engineering Operations and Culture at GitHub, the world’s largest software development platform. Previously, as Chief of Staff for Security, he managed the office of the Chief Security Officer, improving overall business effectiveness of the Security organization through portfolio management, strategy, planning, culture, and values. As a Staff Technical Program manager for Enterprise and Compliance, Ben managed GitHub’s on-premises and SaaS enterprise offerings, and as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →
This page is open source. Please help improve it.
Edit