Design docs - what role do they play in your dev?

Discussion in 'Indie Related Chat' started by moco, Sep 26, 2006.

  1. soniCron

    Indie Author

    Joined:
    May 4, 2005
    Messages:
    3,664
    Likes Received:
    0
    The point of a design-doc (or at least, design notes) for a single developer is simple: it helps you realize your objective with the game and discover any design flaws before you muck up your code with what could be a waste of time. I don't know about you, but I can write up a couple paragraphs far faster than I can whip up a prototype of even a simple idea.
     
  2. David De Candia

    Original Member

    Joined:
    Nov 21, 2005
    Messages:
    89
    Likes Received:
    0
    Hmmm - perhaps there's a confusion between design notes and design documents here. I have no objection to design notes, but a design doc (which to me is comprehensive and much, much more than a couple of paragraphs) just doesn't work for me.

    I'm finding that ideas can be great in theory (on paper if you like) - but just don't play well in practice. I'd rather find that out sooner rather than later. But each to his own.
     

Share This Page

  • About Indie Gamer

    When the original Dexterity Forums closed in 2004, Indie Gamer was born and a diverse community has grown out of a passion for creating great games. Here you will find over 10 years of in-depth discussion on game design, the business of game development, and marketing/sales. Indie Gamer also provides a friendly place to meet up with other Developers, Artists, Composers and Writers.
  • Buy us a beer!

    Indie Gamer is delicately held together by a single poor bastard who thankfully gets help from various community volunteers. If you frequent this site or have found value in something you've learned here, help keep the site running by donating a few dollars (for beer of course)!

    Sure, I'll Buy You a Beer