Engineer

I usually follow this way when starting fresh on anything. Big Picture -> A high level view or a short video or a tutorial showing the full process, what happens when they run a certain piece of code, what they do, just sit, hear and concentrate. Build -> Now, the most efficient way of learning actually starts here, when I start to build a project, I have a good understanding of what I am going to do and not just following a tutorial, but this also becomes asking "what if's? and whys?" as we build it slow, I switch to deep dive modes occasionally. Deep dive: Sometimes, a 10 min tutorial portion here ends up taking over an hour fighting with different variations of the code. And its best to do it now than "let's figure out later", because obviously I know (I never will) if I let that go now. So doing this, makes a 1 day learning plan to 3 day plan unexpectedly, but worth it. The first step seems necessary for me: Usually I compare it with math class in 7th grade (I guess) when teacher introduced us to "Trigonometry" -> I didn't like it, because when I ask what does this tan, sine, cos mean, the answers are "Formula" - ok but why? And when I finally realized in grade 10 these are actually pretty cool stuff used to figure out investigations where we can reveal a lot of info with known data with these concepts, now things clicked. I think for every concept those clicking moments of "why are we learning this" is important and that makes thing far more easier to understand. · I'll know I was right in 2 weeks if: It had worked out so far.