[mgkimsal]

last full time job I had, I blogged almost daily, on an internal system I installed. I was laughed at a bit. Mgr asked for weekly 'status reports' but they always either had too little info, or outdated info. The blog was my daily/hourly notes. Initially I just said "read my blog" for the status update, but that didn't go well, but it helped me summarize.

Meetings? I had the discussion/outcomes in the blog. Tricky SQL or weird edge case decision? I blogged it.

A few months after I left someone said "thanks for writing that - it's been a huge help in figuring out why some of the stuff was done the way it was done". Same person who'd laughed at me for wasting my time. :)

[rixrax]

Right. What you did is you documented (internally) what you did, and related decision chains. Before we used wikis, and way back we just wrote it up on paper and archived in folders. Good job and shame on your co-workers seemingly not engaging to similar activity.

What I was referring to though were public blog postings in teh interwebs. And because they are public, you can’t often include details that would make them usable as a documentation in a way internal blog like yours would work.

As an internal tool for documenting what’s been done, or for debriefing. I think blog etc. is just as good as other methods. It’s the public ones where I sometimes wonder how much they add to pool of noise and useless information which makes it so much harder to find good information.

Or I just need to improve on my googling-fu! ;)