>>82166130
I've been "teaching myself" videogame development this year, and I can empathize wholeheartedly with your struggles.
My approach was to exactify terminology. Once you know the correct names to things, you can format a web of connections. I find your predicament interesting, because I was also teaching myself infrastructure and building maintenance at a point in time.
Big problem in technical fields is the lack of lexical accuracy or standardization. There are different names for different components, and for the same components, be it in the analog or digital domain. And since technology is permutational, you will find that these components have different iterations based off form factors or modules. There is no one "main" heat exchanger. There is no singular "main" game engine, or programming language, or even garbage collecting modality for said programming language. Nobody tells you that software is a bunch of programs recursively pointing to itself, built on several layers of other programs. A "toolchain", "compiler", "garbage collector". All just programs on programs, all code written in layers. I've been slacking on the study, though.
I can understand your position on needing a teacher. When I dive into a subject, I collect the terms, and define them one by one using the web. At some point, you realize how much people aren't explicitly telling you in a tutorial. Knowledge digested by a human, who can teach effectively, with precise words, goes a long way in helping beginners.
Really, before I started teaching myself anything, I was looking into mindmaps, word trees, and how to organize information for study. Personally, I found that autodidactism required a sense, or a practice, or a system for processing and organizing data.