Actually, I wonder what the split is between people who prefer videos vs people who prefer reading?
Actually, I wonder what the split is between people who prefer videos vs people who prefer reading?
That way, people who want a video have a video (with the bonus of something to read-along to), and people who want text have text.
Often I find that with videos:
- I already know some bits and pieces about something - it is quite rare to be coming in 100% fresh to something. So I don't want to have to sit through all the crap I already know, or have to skip backwards and forwards getting past the pre-amble ("What we're going to learn on this course!" "What is <subject>?" etc - if I didn't know what it was, I'd not be here doing the course) or bits I already know.
- Videos make terrible reference material. If you are trying stuff out as you learn you have to pause the video, then if you forget you then need to go back and re-watch the video to re-listen to what was said, perhaps several times. Text is so much easier to flip back and forth from.
- Watching videos often leads my mind to wander and before I know it I am "watching" a video and doing my email/programming/random internet stuff... this basically means I end up ignoring the video and just concentrate on my other real work.
Just as a thought experiment - can you imagine a stack overflow type site where all the questions and answers were in video format? That would be a special type of hell :-)
I couldn't watch this as it needed email registration, but some constructive suggestions:
- have a 100% textual content in nice chapters/sections.
- make the first example of something the absolute minimum-viable-example (don't make it "more interesting" with unnecessary extras).
- After presenting the example, go over it again in extreme detail (especially if new concepts are used) and explain each thing - e.g. What is this YAML thing? What is this param for? Why did we use value X? What does this other param do? What values can it take?
- make additional examples that cover the common other cases that someone might come up against, e.g. doing 1 of something vs doing X of something.
- copy-paste-able snippets for boring boilerplate (e.g. installation of stuff etc) are good++.
- Add a video as an extra demo that cements what was covered in the text. Try not to include any bullshit in the video (intros, jokes, other timewasting etc)
It's like keep watching TV for news to find the tiny bit that you might care about. Much waste of time.
For videos, activities that are more visual, like guitar lessons are more suitable
I noticed this split with a few relatives. I can't stand having to slog through a video when I could just as easily read a transcript or a write-up. Therefore, YouTube is the last place I'll look for informative content.
My younger relatives actively seek out video tutorials and the like, and YouTube is the first place they look.
I would suspect that's because they've had more things read to them than they have acquired the skill/patience/vocabulary/instinct to seek out things to read for themselves.
I guess similarly, without the mental movie to play out the actions they're hearing the words for, it can be easier to watch someone type or watch a program run than to read about that same action
A video tutorial can be great, but it's more about the preparation and pace of the delivery. There are some really great and knowledgeable teachers of tech that I cannot stand to watch/hear. And then there are a number of excellent courses on Udemy (for example) that are 99% video content.
So for me, video _can_ be great.
I love videos if I'm starting out from scratch or if I'm trying to go an exhaustive course on something I've learnt on an ad-hoc basis.
However, if I know the tech or have done a course before, I can't bring myself to finish the video.
Regarding Ansible. I'm new so I'd probably take your course :)
So 9 out of 10 times, I prefer text. But video can also be very powerful!
That might interest you more.