Clearly that is true. That said, that does not mean that one is excused from independent research, just because it is "so much easier" just to ask someone else how or what needs to be done.
It's a good thought to consider that some basic knowledge of assembly language is more than "just a little" useful when approaching the subject of reverse code engineering. This is not generally sufficiently acquired by just reading tutorials and attempting to copy their steps. I conceed that it might be more ego gratifying to "crack" those early programs, but, without any "real" understanding of what the program and/or code is basically doing, you don't really "know" much of anything and certainly not much of real "practical" knowledge for general advancement of your skill set.
I'm simply attempting to
encourage you to spend a significant amount of time, whatever that may be for you, acquiring some of the BASIC knowledge which will stand you in good stead as you wander down the paths through the "darkcode woods," as some of our earliest members were fond of saying. Don't be in that much of a hurry to "crack" when you are only following Setp No. 1; Step No.2, etc. without really having some strong "basic" understanding of what you and the code are actually doing. Believe me, it will save you a great deal of wasted effort in the long run, to spend the time sooner, rather than later.
Patience is a hard trait to master, but it is a necessary one for reverse-code engineering.
Regards,
Hidden in plain sight, I guess.