If the code snippets are useful enough to me, I tend to add them to the repository under some title like "tools" or "scripts". That way other people can benefit

If the code snippets are useful enough to me, I tend to add them to the repository under some title like "tools" or "scripts". That way other people can benefit from them and help improve them if they are useful. Otherwise the knowledge/time dies when I move away from the project. Documentation wise, I use Markdown (religiously keeping it to 80 characters) and Pandoc to build any kind of output. Again, I normally just add this stuff to a Wiki somewhere. I've been terrible at keeping this stuff up to date, but for the most part it acts as a good starting point and either myself or someone else in the team can update it. On a different note, I would be careful about adding content related to work to outside resources (run this by somebody). Personally I like to stay in control and not rely on some relatively small company still being around in 10 years time. Edit: +1 also for using paper and pen for coming up with ideas, etc. Most things start there for me and then end up being digitized.