If you use the term "Open Source" as a verb, you're probably Doing It Wrong. If you develop a piece of software in the open, preferably with a community around

If you use the term "Open Source" as a verb, you're probably Doing It Wrong. If you develop a piece of software in the open, preferably with a community around it, then you won't be able to get away with it being impossible to deploy or containing inappropriately-licensed subcomponents. If you don't, you'll likely run into all of the problems the author mentions, and more, when you go to 'Open Source' it. Not only that, but there'll be nobody to maintain the resulting project, and it's likely that nobody will actually benefit. Open Source is great (FWIW I work exclusively on Open Source at the moment), but it isn't like a condiment you can spread on after the fact. It needs to be baked in to your strategy.