Well, no, not a "long rambling post", which could mean a chunk of your otherwise productive time, but a brief summary report that simply covered:

• Objectives.
• Implementation Plan.
• Resources required.
• Actual Implementation Steps, and variations to plan - in timeline order (or order of occurrence).
• Outcomes.

- could be interesting, but only if the report could also be useful to yourself as a sort of diary note.
In fact, if you already had diary notes about the implementation, then you could construct the summary report from those notes. This is something I often do for myself, so that I can go back and review something I did in the past. My notes nowadays are invariably documented very nicely in MS OneNote, and I can put them up in a public share, rather than send them out as a file or put them up as a document on a website. Blogging the summary in a blog or a forum post would be a relatively tedious exercise - the medium being very limited by comparison to a document, which latter is more suited to being indexed, well-structured with a self-contained TOC, diagrams, etc. and thus more easily read as a report.

Another yes

I am on page 12 of the essay about the server move.. Will post it this weekend.

Mouser Tails



Amazon best sellers list Spring 2018