I mean, it's kinda always been that way. There's this skill cliff you get to between power user and operator where you know enough to solve easy problems but ge

I mean, it's kinda always been that way. There's this skill cliff you get to between power user and operator where you know enough to solve easy problems but getting all the information you need to put it together into something useful requires non-trivial effort. And you go through that cliff every time you take on a new project. If you want to put together a self-hosted Spotify alternative, for instance, one of the first and most attractive things I found was mpd. I put a whole bunch of time into working out how to containerify it so I could run it on my cluster in order to find out why nobody else put in the work, mpd isn't designed to and has no functionality to serve music over a network. It's there to run a local music player. It was written in an era before Spotify and had no idea that was going to be something people would want to do. And you can find online thread after thread of people asking how to do this with mpd and getting answers that aren't satisfying. It leads them to get on a forum themselves and ask themselves, in order to get the same unsatisfying answer. It takes time and experience before you can figure out such things at a glance just by seeing other conversations about it. Time before you learn you need to read the available docs carefully because the answer you're seeking is very very probably in there already. Nobody's born with this kind of patience but working on tech stuff long enough will eventually beat it into you. It's just that more and more people are starting out and so online is simply dominated by these people.