It depends on what the video is about and if I'm watching it on my phone while being on the move or not. But usually it goes like so:

• If the video is showing how to do X with the coding involved and it's something I haven't done or want to have as an example on my laptop then yes I will code while watching it.
• If the video shows codes and explanations around say paradigms or how he/she goes about doing A or B tasks then I would just watch and see how he/she thinks about the problem(s) to solve and how he/she writes the solution (read code).

I find video tutorials to be an easy and efficient method for learning new subjects.

Searching for quality, relevant videos is the first challenge. I generally accomplish this by searching through my youtube subscriptions first, since these are channels I have had positive experiences with in the past. If the content just isn't there, then I search outside of this network. It depends on what I'm looking for, though it usually takes around 5-10 minutes to find a decent set of videos.

Next, I organize these videos into a playlist where each video builds upon the previous one, or where watching the first couple videos would potentially preclude me from needing to watch the rest.

When I am ready to begin the playlist, I set the video speed to 1.25x or 1.5x the original speed and often skip sections of the video to get a decent overview of what will be covered before I commit to watching the entire thing thoroughly. This also primes me to better understand the content if I do decided to rewatch (still at 1.25-1.5x speed).

When I rewatch a video, I take notes and write down questions around concepts that were inadequately presented. I will then proceed through the rest of the playlist taking notes, asking questions, and answering questions I had from previous videos. At the end of this process, I may still have questions. In that case, I will look for answers on StackOverflow, Reddit, Hashnode, etc. to round out my understanding of the subject.

Only after I understand the subject to the extent that I have very few unanswered questions will I begin to code. At this point, I take a more pragmatic approach to the process by running into problems directly and seeking out resources that will allow me to proceed to my end goal.

By the end of this process, I have not only gained a high-level perspective on the subject, but also a ground-level perspective on how to deal with the implementation details of a project.

At first I try to understand the concepts so I watch about 75% of the course . After getting an idea then I make plan what to code in and try to code along with video .

I do it like this:

1. If I have no clue about the topic, I either watch a video in which the persons build something really simple with it. Or I usually read a blog post in which the guy builds something. I usually tend to code along with the blog post. Coding along the video is distracting and hard to accomplish.
2. Once I am comfortable and have a birds-eye view of what that thing really is, I start reading books or more elaborate resources.

Learn from the master, doing things the hard way is actually the right way doing things and learning a thing or two in the process. Jason Knight might give you a great insight into this.

Personally I find video tutorials USELESS. I can't learn a blasted thing from them and they are more of an annoyance than anything else. In fact I watch people try to learn from them and shake my head as not only are the tutorials more often than not wrong, the person in question COMPLETELY misunderstands what LITTLE information is present.

They waste five to ten minutes on concepts that don't even warrant a paragraph of text, they're near impossible to search or cross-reference, often the resolution makes it so you can't even read what little text is present, you waste time on trying to figure out what the different accent or bizzaro-land pronunciations are even trying to say, and on the whole the result is a hot wet sticky useless MESS.

Gimme a book, a website, the actual specifications -- TEXT!!! Then I'm happy.

MAYBE it's because I learned computers some two decades before video tutorials were even a thing, but I don't "watch" tutorials.

That or it could just be my utter lack of tolerance for the TLDR "wah wah, I dunz wanna reads!" mouth-breather twitter-generation, who I imagine just yum up the video tutorial crap.

Hence why when someone asks "what do you think of my video" the first words out of my mouth is "Do you have a transcript?"

tl;dr: don't watch coding tutorial videos.

Imho, videos are a great way to introduce technology and foster discussion by roughly explaining something. So, if I watch a tech video like a video about cloth simulation, I usually watch it several times in whole, not touching any code. Then I take out the papers and try to find some source examples.

For such a process, videos are ideal. However, if you want to learn how to code, they are abysmal. It's one of the reasons why you have books at school. What you see and hear is easy to understand on a high level, but most of humanity has trouble remembering the small details we hear and see. And while it is easy to pause a video to take notes or write some code, it is a lot harder to go back to what the instructor said about something, which might come up while writing code. Just think about looking something up you heard in a previous video. It's hard to find the right place.

Not only is a video hard on you, but it is also hard for the maker of the video. They need to do a very thorough preparation, and be especially careful with every word they say. Our natural language is often quite blurry, so they need to keep to a technical tone at all times, ideally reading down a script. In that case, why not just release the script?

After thinking about problems of both sides, there is another point to consider. How much does the author of a video actually know about what they teach? The internet is vast, and if you just go to YouTube, chances are that someone without a clue is trying to explain an important mechanic to you, getting everything mixed up. As the person who wants to learn, it is hard for you to decide if someone is trustworthy and knows what they do.

To put it into a nutshell: I learned everything I know from the internet. I did try videos, but I learned to stay away from them. They are hard on the learner, difficult and controversial for the presenter and there is a lot of trust-problems with sources to choose from. Don't use videos. Use the official docs, books and written tutorials.

I watch tutorials to understand new concepts, so I watch the whole thing. Many times if needed. If I grabbed the idea, I might try to apply what I learned, but I will not watch along.

Many people making tutorials are like I just do it to explain, but you should pay more attention to how to make that part and do not apply good programming concepts, which is very bad in my opinion.

In my mind, because it's a tutorial, you should code properly every single line of code, it'll be more beneficial...

Unless I'm just reviewing something I already know, I find that coding along side forces me to pay attention to the video more than just watching does.