[avitzurel]

I've never done it for myself. I did, however, do it for screencasting (Twitch and YouTube).

There are a couple of things here:

1. Talking to yourself is extremely useful. You'll be surprised by how effective it is. 2. A recording is not very useful because discovery is awful. Even though all my content is on YouTube, There's no way I can find that one time I fixed an interesting bug or implemented something complicated. Without proper logging of what you did and indexing in the video, it will just be like any other video you take with your GoPro, hours of nothing.

What I found to be really effective with my teams is this: 1. Draw your thoughts. 2. Write up a mini-plan of how you want to "attack" this 3. Talk through it, even if it's only to yourself. 4. Pseudo Code and Pseudo Flows of data

[segmondy]

Interesting... Voice transcription software can close caption and you can search by that. You can have keywords you can use for searching. TODO, BUG FOUND, BUG FIXED, FEATURE X. Perhaps the tech is not yet solid for searching, but I feel that the basic elements is there. I'm more interested in doing this for solo project, but this can be interesting for teams too, what if you can look through a git history and match it up with the video of when it was developed and hear the author's line of thought? The tough part of it of course will not be the tech but the behavior of getting folks to speak up and dump their thinking verbally.