I agree we need easier-to-use documentation on this stuff, but have you considered documenting what you've done yourself? I started keeping a notebook of helpfu

I agree we need easier-to-use documentation on this stuff, but have you considered documenting what you've done yourself? I started keeping a notebook of helpful tricks back in the 90s. By the mid-90s I was publishing some of the info, and by the late 90s I had friends working with me to create articles. This was when the e-Zine was still pseudo-popular as a channel of self-publishing. We later went on to blog format, but the results are the same: Your brain forgets little, but loses references to information it hasn't needed to use in a while. Documenting things (which includes proofreading and maybe even testing your documentation), uses repetition to solidify those references. Some people learn by repetition better than others, but even if it's just penciling apache config tips or iptables examples into a Moleskine journal, writing is often one of the best ways to memorize things. The things I've written down are the things I remember best or at least they're the things I find easiest to come back to. It goes for the awk recipes I've jotted down, database tuning parameters, and even automotive repair tips.