I personally wouldn't use videos to learn coding or technical design. To me one of the necessary exercises--so necessary, it's the main point of it-- is to get used to following precise written instructions, in precise semantics, each term of which is there for a reason--and in fact, is an inherent part of the platform you are learning. The discipline of following constructs like, "Check the
Properties Pane of the
Form in
Design View and identify the
Popup Property" is exactly what is needed to be learned--Learn to ingest information presented like that, and learn to express it like that yourself. That's the only way people in the development world survive, by all speaking the 'same language'-----Not, "click here and then click down here on this gray box with a white space like I'm showing you". There may be a few platforms or scenarios where, for some reason, they are the exception to that 'rule'.
That's my personal opinion that certainly won't be shared by all--and I respect that. However, I try to stay openminded about the issue, as some new learners swear by it. (Then again, I wonder if that's the same people who cannot express themselves in anything resembling correct/understandable terms when the need arises).
I think Pat made a good point. The general idea is you either DO want to become technical in an area or you don't. If you don't, skip it. If you do, commit to it, and to taking an academic approach to it. I do not recommend approaching it with the concept that "I'm going to get to where I can create technical output without being at all a technical person"--All you'll end up doing is making mostly messes at best, or an actual instrument in the loss of fidelity of your employer's data at worst. If you get to that point, it will get worse; you won't know how to ask for help nor troubleshoot the problem.
We all start somewhere, for sure--But knowing what you're in for and embracing it is the best foundation.
A little harsh sounding truths here, I guess. Sorry.