I hate videos. I’d rather read a book with 500 pages than watch a video about anything. Actually, I don’t think I’ve ever watched a technical video in my whole life.

I’m mostly in the pro-written word camp myself, but I have sought out video tutorials in cases where written docs seem to assume something I don’t know. When I’m learning something new, a written doc might have a 3-word throwaway clause like “… add a user and then…”. But I’ve never added a user and don’t know how. If it’s niche open-source software with a small dev team, this may not be covered in the docs either. I’ll go fishing for videos and just seeing that they go to a web-ui or config-file or whatever sets me on the path to figure out the rest myself.

That is to say, video content that shows someone doing a thing successfully often includes unspoken visual information that the author doesn’t necessarily value or even realize is being communicated. But the need to do the thing successfully on-screen involves documenting many small/easy factoids that can easily trip someone inexperienced up for hours.

I’m as annoyed as anyone when I want reference material and find only videos, and I generally prefer written tutorials as well. But sometimes a video tutorial is the thing that gets me oriented enough to understand the written worthy I wasn’t ready to process previously.

Edit: The ubiquity of video material probably has little to do with it’s usefulness though, and everything to do with how easy it is to monetize on YouTube.

deleted by creator

Technical videos have helped me perfect my pronunciation of “umm” and “uhh.”

Demo videos are not “documentation.” They are “demos.”

If you want someone to repeat your steps, it should be code or CLI commands. You can write more descriptive text, but as soon as you reference pictures to show something, you’re introducing ambiguity that text/code can avoid.

UIs change faster than videos and screenshots, as you said, can’t be searched, and are generally less accessible than text.

The source files for documentation should also live side-by-side with the code in the repo. As soon as it goes anywhere else, it immediately goes out of date.

deleted by creator

I like written-form documentation, it means I don’t need to play audio in our shared space at work. It’s also a lot faster to find what I’m looking for with written docs than skipping through a video looking for the relevant bits.

Usually when I’m looking for docs, I find that the less time I need to spend in the material, the better. Videos are fixed length and don’t often come with a list of labelled timestamps.

If it’s a YouTube video, it probably has been made to monetise, not to share tech material. So I usually avoid YouTube, because most of the time it’s not worth it.

I prefer written articles. But for teaching, especially someone who is a junior or novice in the field… Video works better.

So depending on the audience.

Well, obvious reason: you can’t edit an outdated video with easy effort. But with text you can.

But for a tech talk or demo, I’d still prefer a video than written text.

I like Fireship style videos for a quick introduction to a subject, but I avoid videos if I quickly need to find something. Text is searchable and just a lot quicker in general.

Weirdly not many responses are talking about real workspace that much. While written docs are king, video has its own place. Recordings of technical meetings are very valuable and if spoken in english, tools like sharepoint are transcribing them, so you can search them via text. Most often those meetings material will never be written, so video is best second choice.

I prefer written articles

deleted by creator

Videos are not documentation.

They can be used to demonstrate examples of how to do a particular task, but as other commenters have mentioned, documentation involves listing classes, functions, parameters, etc and clearly explaining what they all do, in a searchable manner. Text is searchable, video is not.