<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
         xmlns:thr="http://purl.org/syndication/thread/1.0" 
         xmlns:wfw="http://wellformedweb.org/CommentAPI/">
  <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2005://1.7674-</id> 
  <updated>2007-12-03T11:52:00Z</updated>
  <title>Comments for Shortcomings of expert systems</title> 
  <subtitle>Jack Vinson writes about knowledge management, personal effectiveness, theory of constraints and more.  As of December 2007 Jack will likely start writing about product management too.</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.01</generator>

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2005://1.7674" type="text/html" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.html"/>


    <id>tag:blog.jackvinson.com,2005://1.7674.2900</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.html#comment-2900" /> 
    <title>Comment from Bill Brantley on 2005-11-28</title>
    <author>
        <name>Bill Brantley</name> 
        <uri>http://eclecticbill.blogspot.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://eclecticbill.blogspot.com/">     
      <![CDATA[ <p>Dorothy Leonard and Walter C. Swap describe how expert knowledge is developed in their book, "Deep Smarts: How to Cultivate and Transfer Enduring Business Wisdom" which could explain why expert systems failed.  In describing how experts become experts, the authors write that job experience can be thought of as a Gaussian (Bell) Curve in which a new employee starts in the middle of the curve where the most common job experience is.  As they continue in the job, their ranger of experience grows out toward the tails of the curve where the least probable (but usually most impact) experiences occur.  Thus, expertise is the gradual accumulation of experience that is codified into tacit knowledge.</p>

<p>Because an expert system can only capture the codification of the experience and not the actual chain of thinking resulting from grappling with the new experience, there are numerous hidden assumptions that are not reflected in the codification.  The cookbook is the chef, basically.</p> ]]>
    </content>
    <published>2005-11-28T20:47:44Z</published>
    <updated>2005-11-28T20:47:44Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2005://1.7674" type="text/html" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.html"/>


    <id>tag:blog.jackvinson.com,2005://1.7674.2902</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.html#comment-2902" /> 
    <title>Comment from Matthew Hurst on 2005-11-28</title>
    <author>
        <name>Matthew Hurst</name> 
        <uri>http://datamining.typepad.com/data_mining</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://datamining.typepad.com/data_mining">     
      <![CDATA[ <p>I suspect one aspect of failure or sucess here is how exciting they are. Expert systems were never as sexy as, for example, neural networks. As you say, they may well have found their niche in commerce/research and haven't failed at all.</p> ]]>
    </content>
    <published>2005-11-28T21:01:04Z</published>
    <updated>2005-11-28T21:01:04Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2005://1.7674" type="text/html" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.html"/>


    <id>tag:blog.jackvinson.com,2005://1.7674.2907</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.html#comment-2907" /> 
    <title>Comment from jackvinson on 2005-11-28</title>
    <author>
        <name>jackvinson</name> 
        <uri>http://blog.jackvinson.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.jackvinson.com">     
      <![CDATA[ <p>My thesis work was on expert systems and I know what you mean about the "sexy."  I looked at a sub-genre of expert systems that were model-based, rather than the traditional rule-based.  In my work, I had modeling frameworks which I used in combination with heuristics (rules).  Models were qualitative, based on the work of <a href="http://www.cs.utexas.edu/users/kuipers/">Ben Kuipers's</a>  qualitative simulation tool.  My grad school colleagues also looked at <a href="http://www.cs.northwestern.edu/~forbus/">Ken Forbus'</a> qualitative reasoning work.  My advisor, <a href="http://www.cis.upenn.edu/~ungar/">Lyle Ungar</a>, has been interested in machine learning (neural nets, genetic algorithms, etc) for some time and has moved completely into computer science.</p> ]]>
    </content>
    <published>2005-11-28T22:14:07Z</published>
    <updated>2005-11-28T22:14:07Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2005://1.7674" type="text/html" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.html"/>


    <id>tag:blog.jackvinson.com,2005://1.7674.2921</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2005/11/28/shortcomings_of_expert_systems.html#comment-2921" /> 
    <title>Comment from Denham on 2005-11-28</title>
    <author>
        <name>Denham</name> 
        <uri>http://denham.typepad.com/km</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://denham.typepad.com/km">     
      <![CDATA[ <p>For me the big failure of ES was their inability to adapt and learn. Sure you can cycle between inductive and deductive reasoning, but the brittle nature comes from not understanding the world, from a lack of sense-making and from working within a very small fixed domain.</p>

<p>True insights come from mashing, hashing, satisficing, ripping, mixing and from failures. </p>

<p>I wonder how CyC is helping with adding some common sense to the ES scene these days?</p>

<p><a href="http://en.wikipedia.org/wiki/Cyc">http://en.wikipedia.org/wiki/Cyc</a></p>

<p>It was the little, inconsequential, trivial things that made ES look dumb. So my vote goes to a lack of robustness as the chief failing of ES.</p> ]]>
    </content>
    <published>2005-11-29T02:55:52Z</published>
    <updated>2005-11-29T02:55:52Z</updated>

  </entry> 

</feed>
