When you go into a carpentry workshop, there are hundreds of tools, all designed to work on wood, and a carpenter will know the majority of their tools quite well. They can invest in a tool knowing they can re-use that knowledge for the rest of their career.
When I inherit a software project, it can often have two, three, even four different language ecosystems involved with hundreds of libraries and tools as dependencies. In software we have to accept that we will be surrounded by dozens of tools we need to work with but will never have time to fully master.
Most people I meet are only proficient in many of their tools enough to get the job done and no more. Soon enough the status quo will change and the software industry will happily drop thousands of man-hours of learning right into bin.
The finer points of library X, framework Y, or tool Z are almost ephemeral. Even a company's core software product could just be thrown away and re-written in the new-hotness at the behest of a PM meeting, often losing nuanced domain knowledge in the process.