Find a good doc / book / whatever, and then read the TOC.
When there is no TOC, instead speed read the headings in a doc - hit page down (spacebar) a bunch of times as fast as you can to get the main keywords / concepts to stick.
For me knowing that a particular concept / tool / technique / thing exists and where it's documented if I need to know more is the primary technique. Go deep on a few fundamental things next, then work out what you want to do with the tool and work on that and the surrounding necessary topics to achieve that task.
Often ramping up fast is akin to finding ways to traverse the knowledge graph of prerequisite knowledge. Knowing how to speed up that is the best meta skill you can develop.
In my 20 odd years as a software developer, I've found it very rare that I'm working on a task where I start with the knowledge to complete it.
That approach works for me - it might for you too?
When there is no TOC, instead speed read the headings in a doc - hit page down (spacebar) a bunch of times as fast as you can to get the main keywords / concepts to stick.
For me knowing that a particular concept / tool / technique / thing exists and where it's documented if I need to know more is the primary technique. Go deep on a few fundamental things next, then work out what you want to do with the tool and work on that and the surrounding necessary topics to achieve that task.
Often ramping up fast is akin to finding ways to traverse the knowledge graph of prerequisite knowledge. Knowing how to speed up that is the best meta skill you can develop.
In my 20 odd years as a software developer, I've found it very rare that I'm working on a task where I start with the knowledge to complete it.
That approach works for me - it might for you too?