Slashdot Mirror

← Back to Stories (view on slashdot.org)

Documentation Strategies?

Posted by Cliff on from the getting-it-all-down-on-paper dept.

An anonymous reader asks: "I'm a developer and have been given a task of creating documentation, for fellow developers, on how the system (a CMS) I have implemented, and adapted, works and how to develop for it. On the surface it doesn't seem too complicated but the amount of information I need to get down on paper, and the level of detail needed on some parts, is great. What's the best way to approach this task when there's so much information bouncing about in your head you don't know where to start?"

3 of 55 comments (clear)

  1. Dude, you're being outsourced!!! by bergeron76 · · Score: 2, Funny

    Trust me.

    So you're the CEO or one of the Chief officers? Don't worry. Your job can be outsourced too!

    --
    Don't think that a small group of dedicated individuals can't change the world. It's the only thing that ever has.
  2. Re:Ask Slashdot by horati0 · · Score: 3, Funny

    Why does it burn when I urinate?

    Because you're not writing documentation correctly.

    --
    The neutrality of this sig is disputed.
  3. Documentation?!? by The+Angry+Mick · · Score: 2, Funny

    Why do you think they call it "code"?

    --

    I'm not tense. I'm just terribly, terribly, alert.