How to reduce some of the risk of relying on third-party software

Image for post
Image for post
Photo by Zoya Loonohod on Unsplash

In How to Choose the Best Open Source Module For Your Needs, I spoke about a number of principles we can use to choose the “best” open-source module for our software projects. This process is not entirely foolproof, however, and there are additional defensive measures that can be taken. This article describes an approach I have used successfully. We’ll look at why it’s even necessary in the first place and consider some limitations. I hope that it benefits you as well, or at least stimulates some new ideas.


There are so many! Which one do I pick?

Image for post
Image for post
Photo by Victoriano Izquierdo on Unsplash

I really appreciate the current state of open source development. It may not be perfect, but I truly value the free flow of ideas and creativity, and the willingness of so many developers to share what they know and how they solve problems. Ultimately, this is what I think open source should be: solving problems and sharing answers.

However, as with almost everything in life, this coin has another side: Not all answers are equal, and having too many choices can be almost as bad as not having any at all. Once I started writing software that relied on open source modules, I learned this reality pretty quickly. I eventually came up with a set of guidelines to help me make decisions and mitigate some of the inherent risk. …

About

David Passarelli

I help small IT teams to streamline and accelerate their product delivery pipeline. I write about OSS and what I’ve learned along the way. dpassarelli.github.io

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store