3 ms·
I've tried that, but I found that writing a tutorial consumes too much time when writing for a wide audience. So, I started writing tutorials for myself. It's b
by dschuetz 8y ago
I've tried that, but I found that writing a tutorial consumes too much time when writing for a wide audience. So, I started writing tutorials for myself. It's brief, covering the most important steps which do not explain much, but it gets the job done. That way I needn't going through the research process all over again for the same thing I did some years ago. Later I might decide to share that knowledge, but again, editing it for a larger audience costs time.
- jypepin 8y agoyes this is what I do. I have a blog, that nobody reads. I write about tech and non-tech things, without stress of fears, because I only write for myself, like my personal, public notepad. Sometimes I talk to or help someone and remember a post I wrote that could help, and share it.
- Jaruzel 8y agoSame here. If I need to learn something technical (new language or platform etc.) I build out a Word document with proper headings and dump all the keep info into that. They are not tutorials per se, but they make sense to me and once written I end up knowing far more about the subject in less time, than if I'd just read about it online. The sheer act of re-writing down the information helps me commit it to memory.