I wanted to start another thread because I agree with @Peter Jakacki
and given my posts, that didn't make sense! @pilot0315
may find this discussion of interest too.
Basically, the approach I put out there is for people seeking more "what is what." It's about knowing what you don't know, and it's also about priority. But, people really do learn differently, so hold that thought.
After I wrote it, on my drive in I actually was thinking about FORTH, how Peter works, and that method not working well at all. Thankfully, he chimed in triggering this discussion.
The method I outlined is most useful for assembly language programs. It's utility becomes marginal the more structured and clean a language is, and the more interactive a language is.
Some of you may argue FORTH is not clean, or jokingly refer to it as a write only language, but I disagree. The actual core of FORTH is ultra simple. And given an approach like Peter uses, is very lean, clean and mean too.
I know @pilot0315
wants to learn assembly language. What I didn't know was their overall level skill may be a bit beyond where it works well. Happens!
Both @Peter Jakacki
and I subscribe to the interactive school. "Just try it" really has value. There is the agreement.
Both of us are missing a little bit of what @pilot0315
needs, which is context. An operating system, loader, linker, and all that, from an assembly language, and P1 point of view, could be pretty confusing! More discussion is needed there, IMHO.
So, let's have a talk about how you learn how to learn! Others will benefit.