This story was originally published on HackerNoon at:
https://hackernoon.com/how-to-choose-a-dependency-build-vs-buy-risk-management-and-more.
In this post, I'd like to describe my approach when choosing a dependency. I'll first define what I mean by dependency in the context of this post.
Check more stories related to programming at:
https://hackernoon.com/c/programming.
You can also check exclusive content about
#coding,
#dependency,
#what-is-a-dependency,
#build-vs-buy,
#risk-management,
#dependency-choice-criteria,
#dependency-in-coding,
#hackernoon-top-story, and more.
This story was written by:
@nfrankel. Learn more about this writer by checking
@nfrankel's about page,
and for more stories, please visit
hackernoon.com.
A dependency is literally something your software depends on: infrastructure such as a filesystem or a database, network, etc. In this post, I'd like to narrow the scope to a software dependency that you need to compile/run, *i.e., a library. I'll first define what I mean by dependency in the context of this post. Then, I'll list a grid of several criteria to analyze possible dependencies.