This blog attempts to do several things, including: being a somewhat applied creative writing outlet (in previous jobs, I did a lot of writing; I kind of miss it); documenting things in case I need to redo them or wonder how the hell I did that thing 5 years ago (although I have also set up and extensively use an in-house MediaWiki for internal documentation); last, but not least, "giving back" to the community at large. I have learnt countless things over the years simply by reading about them on the Internet, and of course by "hacking" (in the old "Unix hippie" sense) away at things. Somebody put them there. This is my small contribution to repay/service that kind of "debt".
The only thing better for building and retaining knowledge than doing-it-yourself and documenting a solution (or contributing code or script if you have talents in those areas) is teaching it to others. Even if you're not a member of teaching staff, start a computer club that teaches interested kids what you think is important - focusing on practical things they can play with which they'll find useful day-to-day or as they go off to pursue careers of their own - whether IT related or not. In particular, if you're lucky enough to work in a team, take time to coach, mentor and train any fellow staff members, particularly junior ones (and in turn, never be closed off from the idea that others have plenty to teach you). Yes, you risk one day "loosing" them to a better paid position, but I think there is deep wisdom in the concept of the "cost" of NOT training people!
Topics will obviously be biased by what technologies I play with or have access to. I might like to write a manual for an arcane, expensive piece of gear, but if I can't play with it, I can't write about it! For the most part, by applying some "lateral thinking" you can often adapt a technical guide to a slightly different set of tools.
Hopefully, others will find useful guides or insights in these virtual pages!
Do leave comments if you wish to; it's always nice to know you're not simply "howling into the void"! I'll address those I can, as and when I'm able in amongst my duties, or when I notice comments have been added.