Earlier in this series, we explained how innersourcing can solve common enterprise challenges, the benefits of releasing early and often, and the efficiency of microservices architecture. In this final post, I’d like to share my thoughts on an exciting new trend: open source practices expanding into a variety of industries. Over the past year, we've seen more and more companies are engaging with open source.
Many companies benefit from open source, and countless companies have opted to open source components of their infrastructure (or even their bread and butter) in an effort to give back. However, there are a lot of misconceptions about what happens when you open up your business' code and workflows to the public, and as companies delve into how to apply open principles within their organization, it's easy to get lost in the weeds. Here are some common misconceptions about what happens when you open source your code.
We’re starting a series of posts that explore existing and growing trends in version control. This week we’re looking at innersourcing.
As a follow-up/update to a post we did on innersourcing back in 2014, we’ll be looking at what innersourcing is, who’s using it, and how it’s solving some of the biggest problems enterprise developers face.