One reason I really like open source is that it offers a lot of great opportunities for newish programmers to get some hands-on experience with real world problems. There’s only so much one can learn …
Open Source Explained — Open Indie
Musings on the concept of ‘open source’, in the broadest possible definition of the term. Also an invitation to become a participant in ...
Why open source: 25 reasons to embrace it | Ben Balter
Open source isn't a fad. Here are twenty-five economic, moral, and personal reasons your organization should embrace it.
How open source projects need to adapt to the AI coding era | We Love Open Source • All Things Open
A new Carnegie Mellon study shows AI coding tools boost velocity by 281% — then leave codebases harder to work with. Here's what open source communities need to do before the sugar rush wears off.
Embrace Open Source, For the Good of Nerdmanity | Fortune
More businesses are willing to use open source software for key projects.
Get In, Get Out
open source advice for new programmers breaking into the industry
The Great Open Source Debate: 4 Things to Consider
Build, deploy and manage your applications on any cloud or your own servers.
What We're No Longer Seeing: AI and the Invisible Newcomer in Open Source
How AI is absorbing the visible friction that open-source communities have always relied on to see—and welcome—newcomers.
Passive Open Source
I used to be an active contributor to open source projects, but that was when I was still in college - I had a lot of free time and it was some good learning experience. I even managed to get involved with several open source projects when I start my first job in a big company.
What Is Open Source Strategy? — Open Tech Strategies | Blog
There is a lot of documentation out there on how to do open source well at the project level. Historically, many projects have been started by developers, often on their own initiative, and the first non-technical questions they faced tended to be about project coordination (like "What collaboration tools shall we use?" or "What will our code review practices be?") and about community management (like "How do we decide who has commit access?" and "How do we integrate newcomers smoothly?"). Because developers hate to solve the same problems over and over, there is a wealth of detailed and varied material addressing those sorts of questions (we've even written some ourselves, but it's just a drop in the bucket of what's available). Taken together, this literature thoroughly answers the question "How do we execute the best tactics for developing open source software?"
Twelve tips for growing communities around your open source project | Ben Balter
Publishing code isn't enough. Twelve practical tips to attract users, welcome contributors, and grow a healthy open source community.
Open source is 20: How it changed programming and business forever
"The reward of victory is often another set of battles."
Open source and the software supply chain
Managing something as esoteric as resources for building software with a variety of contributions made by the open source community is more amorphic.
The shape of open source
At its core, open source is about collaboration. Whether it’s version control, licenses, or issue trackers—everything exists to support people working with each other. Open source embodies a model for…
I hate the term “open source”
It doesn’t accurately reflect how people are building today anymore.
