I agree it's not always possible. In this case it was possible and someone did explain it in a sentence or two in another response to my question. In most cases

I agree it's not always possible. In this case it was possible and someone did explain it in a sentence or two in another response to my question. In most cases it's possible. Here's the opportunity: I've been programming for decades. I'm always on the lookout for new and better solutions. I might not have a use for the software today, but if I can understand what it does and bookmark it, there is a good chance I will come back when I do need to solve that problem. This means a lot to me and allows me to bookmark it both mentally and in my browser: "This package helps reduce DataDog (<-- link) costs by aggregating data before sending and increases monitoring reliability by being distributed and fault tolerant." Pretty much plain English, and now I can bookmark it because I know I will be evaluating my monitoring needs in a few months. I read the entire README and had no idea what the software did. At first I thought it might have something to do with RxJS and observables... > This particular project is probably only useful to people who know what observability data means. Sorry if I'm repeating myself, but no, it's useful to other people. Like me. The software might be useful to me because I am interested in monitoring an app pretty soon. I've never heard someone call it "observability data".The Wikipedia article on observability left me even more confused. This happens a lot, and it's a mistake that can usually be fixed, which is why I wanted to point it out. If it can't be fixed and the software truly is extremely niche, then zero problem.