3 ms·
Tutorials are best for beginners. They start from zero, so the author can build one bit of knowledge on top of another. It's easy for the user to feel progress,
by BraveNewCurency 14y ago
Tutorials are best for beginners. They start from zero, so the author can build one bit of knowledge on top of another. It's easy for the user to feel progress, because every few minutes a new idea/concept can be introduced and explained (at a high level).
It's harder to make a tutorial for an expert. Different experts will know different things, so it's unclear how much time to spend explaining any particular concept. It's harder for users to feel like they are progressing because: 1) it takes much longer to get a "unit of knowledge" across because the concepts are more complex. 2) you are really "filling in the gaps" of stuff they already (partly) know, and they may not even know how many gaps they have. So progress is harder to see and measure.
Random brainstorms:
- Different people learn different ways. Some people want to learn via audio, some via video, some via text, some via diagrams, some only learn by hands-on doing.
- Talking is pretty low-bandwidth compared to reading. That usually includes most video, since it's just video of someone talking, sometimes with a few low-bandwidth slides.
- Staring at talking heads is boring. Partner with an artist to create animations and diagrams for your talk.
- You could try an "expando" tutorial: One that can give high-level details to novices, and expand into nitty-gritty details for experts. I'm not sure that would work in video, but it could work for text or diagrams.
- Or maybe you could try something like "VH1 pop up videos", where a novice could listen to the talk, while an expert could be reading all the sidebars while listening to the talk.
- Each of the areas you mention (learning programming, learning kernel internals, etc.) is a world of it's own that would take a long time to make materials for. You could start by re-purpose existing content (technical blog posts, "Open Source Architectures", etc) to turn into a "video explanation". This would be a quick way to get started and see if you have a useful concept.
- jfaucett 14y agothanks for the extensive post and brainstorming ideas! I agree with you that most people learn different ways, and as others have stated, really learning by doing is high up on the list. I like your thoughts of interactivity, because ideally that's what the tutorials would be like - interactive media, but the thing is, like you say this is time consuming, and sadly, I don't have the time to commit that it would take. One thing I do like about video, at least for programmers, is that - if you're dual wielding with your monitors :), you can watch the code directly, have your own editor open and just code along, while you listen to the expert in his field explain some concepts that might be fuzzy for you. What I don't like though is reading blog post, because honestly all I ever end up doing is just reading the source code excerpts, and then (if its js, or some smaller lib), I just download the source and read it which renders the point of having a blog post basically null and void. Finally, your last idea "repurposing content" is great, it'll let me test the idea out :)