Tech Word

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Monday, 11 February 2008

The Incomplete Guide to Gödel

Posted on 13:24 by Unknown
Kurt Gödel was an Austrian-American mathematician who lived from 1906 to 1978. He’s best known for his incompleteness theorems, which have had a tremendous impact not only on mathematics but on other sciences and even philosophy.

Gödel’s theorems were actually a response to the ideas of another mathematician, David Hilbert. Hilbert had a dream of creating a complete, accurate and consistent system for all the mathematical principles (or axioms) that had been discovered to date. Earlier, some of these axioms were discovered to be wrong, so there was tremendous pressure to ensure such errors would never occur again. Hilbert wanted to establish a solid foundation for all mathematics, now and forever.

Sounds like a great idea right? There was just one problem – to create such a “perfect” system is impossible, and Gödel proved it. He demonstrated that if you created a complete system that described every mathematical truth, it would contain some statements that could not be proven. In other words, the system would be complete but not fully predictable or accurate. Conversely, you could create a system that is fully provable, but then it would not be complete.

How Gödel did this is incredibly complex, but I will try to explain. He essentially created a mathematical system using a complex numerical notation, where one of the statements in the system was: This statement cannot be proven.

Now, if this statement could not be proven, then the system might be complete, but it would contain a non-provable statement, making the system itself inconsistent. But, if the statement is provable, then it means the system still contains a non-provable statement (because the statement itself says it can’t be proven) and therefore the system itself is still not fully provable.
As a workaround, we could just leave this pesky statement out of the system, because it's causing so many problems. However, if we do that, then the system would be missing a statement, making the system fully provable (yay!), but incomplete (boo!).

To summarize, Gödel was saying that any system can be:


  • complete but not fully provable
    or
  • fully provable but incomplete

    This was Gödel’s first incompleteness theorem. His second theorem went further and said that any system can never be complete. That is, any system containing true statements will always be missing some statements, but you can never know what they are. (If you did, then they wouldn’t be missing, would they?)

    The philosophical impact of Gödel’s theories are enormous. Extrapolating his ideas, it means that we can never know everything, and that even if we could, some of what we know could never be proven.

    The implications for information developers should be clear. All documents are essentially collections of statements, namely theory and procedures. It is impossible to create a document that is complete, and we don’t even need Gödel to show this. Users are complex beings and therefore completely unpredictable. Compounding this is the fact that the product being documented (especially if it’s software) is also unpredictable. Mathematically, we would express these two facts as:

    user unpredictably x product unpredictably = lots and lots of unpredictably

    It is therefore impossible to create a complete guide that would explain every possible situation. Even if you could, it would contain statements that are not true. Again, we don’t need Gödel to prove this. Too often we see guides that try to be complete, and in doing so sacrifice quality and accuracy. That’s why the mantra of every tech writer when responding to pressure to quickly complete the draft should be: “Do you want it fast or do you want it right?”

    More importantly, if you really did try to create a complete guide, it would have a size approaching infinity, which is a rather large number. Some of the best examples of documentation are quick start guides, usually just a few pages, or as a fold-out poster. Size does matter, but not in the usual way, because less is often much, much more.

    This column is now complete, but of course I cannot prove a word of it.
  • Read More
    Posted in math, philosophy | No comments
    Newer Posts Older Posts Home
    Subscribe to: Comments (Atom)

    Popular Posts

    • Six Things That Should Be Single Sourced
      Single-sourcing, as we all know, is the art and science of using a single repository of information to produce multiple outputs. Typical ex...
    • Interviewing and Dating: A Single Source Solution
      Last month, people celebrated "Valentine's Day", a day to celebrate romance and love, a day to be extra-nice to your partner, ...
    • The Power of Words
      There's nothing like an election to illustrate how powerful words are. Politicians, pundits, and the media use words to advance their ca...
    • The Governing Dynamics of Documentation
      Game theory is a specialized field of mathematics that analyzes choices and results in strategic situations, or games , as the players try t...
    • Why info systems fail
      If you only have time to read one news article today, read this one from the Financial Post. Don't leave IT to the techies - Three probl...
    • How to update a document - NOT!
      Canadian International Co-operation Minister Bev Oda needs to work on her document management skills. She hand wrote the word 'NOT'...
    • Publishing for Pollard
      Most of you probably have never heard of Jonathan Pollard, the American who has been languishing in prison since November 21, 1985, almost 2...
    • The Dynamic Blogger
      Some of you may have noticed the new look of this blog. It's a new Blogger feature called dynamic views . You can now choose how this bl...
    • Dude, where's my document?
      Try this experiment: Think of a printed guide you worked on. Find the source document from your current location. Make a minor change to the...
    • Security breach!
      It's always entertaining to read about non-lethal lapses in security at a major event. Remember the debacle at the 2010 Winter Olympics?...

    Categories

    • art
    • autism
    • bad communication
    • business
    • career
    • cloud computing
    • computers
    • creativity
    • entertainment
    • finance
    • food
    • Google
    • history
    • interviewing
    • math
    • media
    • medicine
    • misc.
    • music
    • nature
    • news
    • philosophy
    • politics
    • quantum theory
    • religion
    • resume
    • resumes
    • science
    • security
    • simplicity
    • sport
    • technology
    • usability

    Blog Archive

    • ►  2012 (9)
      • ►  September (1)
      • ►  August (1)
      • ►  July (1)
      • ►  April (2)
      • ►  March (2)
      • ►  February (2)
    • ►  2011 (36)
      • ►  December (2)
      • ►  November (2)
      • ►  October (6)
      • ►  September (2)
      • ►  August (4)
      • ►  July (5)
      • ►  June (3)
      • ►  May (6)
      • ►  April (2)
      • ►  February (3)
      • ►  January (1)
    • ►  2010 (47)
      • ►  December (3)
      • ►  November (6)
      • ►  October (4)
      • ►  September (2)
      • ►  August (1)
      • ►  July (2)
      • ►  June (2)
      • ►  May (3)
      • ►  April (5)
      • ►  March (11)
      • ►  February (7)
      • ►  January (1)
    • ►  2009 (36)
      • ►  December (11)
      • ►  November (5)
      • ►  October (4)
      • ►  September (2)
      • ►  August (2)
      • ►  July (3)
      • ►  May (1)
      • ►  April (3)
      • ►  March (2)
      • ►  January (3)
    • ▼  2008 (24)
      • ►  December (9)
      • ►  November (1)
      • ►  October (7)
      • ►  July (1)
      • ►  June (1)
      • ►  May (1)
      • ►  April (1)
      • ►  March (1)
      • ▼  February (1)
        • The Incomplete Guide to Gödel
      • ►  January (1)
    • ►  2007 (10)
      • ►  December (1)
      • ►  November (2)
      • ►  October (4)
      • ►  August (1)
      • ►  March (1)
      • ►  January (1)
    • ►  2006 (4)
      • ►  September (1)
      • ►  June (1)
      • ►  April (1)
      • ►  February (1)
    • ►  2005 (10)
      • ►  December (1)
      • ►  November (1)
      • ►  October (1)
      • ►  September (1)
      • ►  June (1)
      • ►  May (1)
      • ►  April (1)
      • ►  March (1)
      • ►  February (1)
      • ►  January (1)
    • ►  2004 (9)
      • ►  December (1)
      • ►  November (1)
      • ►  September (1)
      • ►  June (1)
      • ►  May (1)
      • ►  April (1)
      • ►  March (1)
      • ►  February (1)
      • ►  January (1)
    • ►  2003 (9)
      • ►  December (1)
      • ►  November (1)
      • ►  September (1)
      • ►  June (1)
      • ►  May (1)
      • ►  March (1)
      • ►  February (1)
      • ►  January (2)
    • ►  2002 (3)
      • ►  December (1)
      • ►  November (1)
      • ►  October (1)
    Powered by Blogger.

    About Me

    Unknown
    View my complete profile