When learning new topics, we always ask questions we can’t find answers to. “Why are there two APIs that do seemingly the same thing?” “How do I achieve this goal?” “Why does this code not work even though it looks similar to the example?” As we research and get more familiar with tools, we gain understanding. At some point, we become experts and know how to answer earlier questions. But it’s worth covering how we get from point A to point B to help others make progress, too. In my experience, it’s common that the answers seem obvious post-factum, but there’s a missing link between facing questions and knowing the terms to look for. Usually I have to get familiar with the project architecture, read its code, look at what it interacts with, scan the bug tracker, etc., before I built a model in my head that answers my questions. And then I discover that the model is easy to understand and has docs, and I agree with experts that it’s a reasonable and well-designed model – forgetting that I-the-novice failed to find it despite the documentation existing!