{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"How to Choose a Dependency: Build vs Buy, Risk Management, and More","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/dfb6d3b0\"></iframe>","width":"100%","height":180,"duration":681,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/how-to-choose-a-dependency-build-vs-buy-risk-management-and-more.\nIn 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.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            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.\nThis story was written by: @nfrankel. Learn more about this writer by checking @nfrankel's about page,\n            and for more stories, please visit hackernoon.com.\nA 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.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}