Fun fact, I thought I had already written this post, but when I wanted to reference it, I found out that I didn’t. 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. Then, I’ll list a grid of several criteria to analyze possible dependencies with.   What is a dependency?   A dependency is literally something your software depends on: infrastructure such as a filesystem or a dat

Frankel's platform  covers topics related to software development, technology trends, and coding tutorials. Through articles, tutorials, and personal anecdotes, Frankel offers insights into programming languages, development frameworks, and best practices in software engineering. Readers can learn about software design principles, development methodologies, and emerging technologies to enhance their coding skills and build high-quality software applications.

A Java geek

A comprehensive framework for evaluating software dependencies before adding them to your project. Covers critical decision criteria including licensing, governance models, project maturity indicators, community activity metrics, support options, developer experience, and market adoption. Emphasizes treating dependency selection as a risk management exercise with ongoing monitoring rather than a one-time decision.

Choosing a dependency