???: " > >From what I understand, the biggest roadblock to writing good code is " > trying to write code too soon before the logic is all mapped out. Javilk: " That is why a LARGE portion of the American software projects fail. " I've done it many ways. I call it "drawing the boxes", and do it till I " know the structure clearly in my head without the paper. That's pretty much the way I prefer to do documentation projects, both print and web-based. I figure out what folks are going to do with it, then I write what I'd want if I were doing that for the first time. Ideally, I watch real-life users doing whateveritis the way they do it now, without the hardware or software that I'm documenting. Then I work through the task myself with the new whatsit until I know exactly how to make it from point A to point B without getting stuck at C-prime. If I don't take the time to plan the docs (or the standard operating procedures, or the business strategy presentation) from beginning to end, they come back and bite me. Hard. Every time. No problem with offsite projects---what they don't see they don't worry about. Gets a bit stressful with onsite projects, though. People don't want to pay for any time not spent clicking away on a keyboard. Ick. K@ [EMAIL PROTECTED] Kat Nagel, MasterWork Consulting Services Technical writing | Editing | Conversions | Webstuff "The transformation of calories into words, of words into money, and of money into calories again are the three cycles in a freelance writer's metabolism." /Mary Kittredge, _Poison Pen_ ____________________________________________________________________ -------------------------------------------------------------------- Join The Web Consultants Association : Register on our web site Now Web Consultants Web Site : http://just4u.com/webconsultants If you lose the instructions All subscription/unsubscribing can be done directly from our website for all our lists. ---------------------------------------------------------------------
