Writer's Block
-
I love writing, and often get quite carried away once I get started, but right now I can't get started. I need to deliver some documentation for a reporting application I've just delivered. It includes some KPI reports, KPI 'master' data, and daily figures (and their totals), with capture and edit screens for all data. I'm stuck on my opening line, and I think once I get past that, I'll be cruising nicely. Here is is, please attack it and leave me some pieces to collage a better one with: The Nkomati Production KPI Reporting application provides production KPI reports on demand, and on schedule, and also facilitates the maintenance and capture of static and daily data that these reports are built on.
Simple: consciously decide to write bad documentation first. Get going. Then go back and clean it up. Don't be afraid to have your first draft begin with a sentence that's leaden, cryptic, or awkward. When I do this, I often find that the "bad" version is much better than I thought it would be.
-
Simple: consciously decide to write bad documentation first. Get going. Then go back and clean it up. Don't be afraid to have your first draft begin with a sentence that's leaden, cryptic, or awkward. When I do this, I often find that the "bad" version is much better than I thought it would be.
Good advice. I've adopted the motto, "Progress before perfection", to help deal with my problem of not doing something not perfect, but it's an ongoing struggle to stick to it.