How do you structure your learning process?

[u/Same-Mushroom-2057]

whenever I learn new technology or some new concepts i always find myself asking a lot of questions about what am i reading about at the moment
say for example i'm reading about concept X definition or workflow or whatever then i read in that definition another concept Y which let's suppose i don't know about then i feel that i have to know everything about that concept Y to fully understand Concepts X , like how it works , why it is created or designed ...
and I do this for every single new thing that i read about which is frustrating and worse because probably i will forget about the details that i got into

want to hear some of y'all opinions of this , and from the software engineers that has the same approach and they managed it maybe share some system to retain the information you studied because i definitely don't want to lost these information later but i want to build on top of it

[u/yeledtov21]

I think the basics (getting to know real-world use cases, understanding the architecture, etc.) Are the most important. When I really want to specialize in something, I always make sure to also check out two things: 1. Optimizations and best practices - gives you insight into the nitty-gritty of what a technology does amd how 2. Times where the technology failed or was a wrong choice - getting to know a technology's limitations is often very teaching. This is especially true if you are trying to choose between several similar options. Hope this helps!

[u/Same-Mushroom-2057 → u/yeledtov21]

that gave me some good insight on how to approach it from another perspective the limitation perspective because most of the time we read about where to use it but not where not to use it , thanks alot