THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: January 15, 2003 02:54 PM Wednesday; Rod Welch

Eric Armstrong appreciates attribution for work on OHS/DKR.

1...Summary/Objective
2...Attribution CDR Specs for NODAL Based on Eric's CDS Specs
3...OHS/DKR Knowledge about Knowledge Management Comes from Experience
.........Licensing Has Not Delayed Progress on OHS
.........OHS Code is Not Available Shown By Lack of Work Product
......Nobody Can Find Anything Project Specs Lost
......Specifications for OHS May Exist in Multiple Views
......KM Projects Failed to Meet Expectations
......Eric Can Advance KM by Reviewing POIMS and SDS Planned on 001126
4...Attribution Key Element of Knowledge Repository
5...Knowledge Management Implemented by OHS Difficult to Design and Build
6...SDS Meets OHS Objective to Augment Intelligence for Creating Knowledge
......Doug Engelbart Has Not Delayed Work on OHS/DKR
......OHS/DKR Can be Implemented by People with Skills and Time
......Open Source Development Fractures Rather than Focuses Efforts
......Volunteers for Open Source Need Evidence of Potential Reward
......Busy Not Enough Time to Invest to Develop OHS?DKR Project

ACTION ITEMS.................. Click here to comment!

1...Eric's letter on 030111 says "someone seems to have misplaced

CONTACTS 
0201 - Armstrong Consulting                                                                                                                                               O-00000767 0101
020101 - Mr. Eric Armstrong                                                                                                                                               O-00000767 0101

SUBJECTS
Specifications for OHS/DKR Requested
Find Anything Too Hard Need Search Engine
Find Everything Clues Design KM Solve Eric's Problem Cannot Find Anyt
CDS Requirements, OHS Specs
Request Help Finding Specifications on OHS
Technology Template Project, Doug Engelbart
Launch OHS Architecture, Doug Engelbart
CDR Specs Published, Lee Iverson
Iverson, Lee Developed NODAL and CDR Based on Eric's Work Developing
Attribution Eric Appreciates Recognition that Lee Iverson Developed N

1612 -
1612 -    ..
1613 - Summary/Objective
1614 -
161401 - Follow up ref SDS 54 0000, ref SDS 45 0000.
161402 -
161403 - Eric appreciates recognition for his work on the OHS/DKR, ref SDS 0
161404 - GU9N, and feels Doug Engelbart affected his progress. ref SDS 0 SL77
161405 - Eric does not recall asking for help to find a specification reported
161406 - "misplaced" on 030111.  It is "overkill" to make an issue on this, but
161407 - understanding how people forget things helps illustrate how to improve
161408 - productivity, which is an objective for an OHS. ref SDS 0 1U87
161409 -
161410 -
161411 -
161412 -
161414 -  ..
1615 -
1616 -
1617 - Progress
1618 -
161801 - Attribution CDR Specs for NODAL Based on Eric's CDS Specs
161802 - OHS/DKR Knowledge about Knowledge Management Comes from Experience
161803 -
161804 - Follow up ref SDS 54 E44L.
161805 -
161806 - Received ref DRT 1 0001 from Eric responding to the letter,
161807 - ref DIP 1 0001, that commented on Eric's letter, ref DRP 2 0001
161808 - received on 030111. ref SDS 54 5M3H
161809 -
161810 - Submitted email linked to this record responding to Eric's letter.
161812 -          ..
161813 -         Licensing Has Not Delayed Progress on OHS
161814 -         OHS Code is Not Available Shown By Lack of Work Product
161815 -
161816 -         Follow up ref SDS 54 656G.
161817 -
161818 -         Eric does not comment on license issue being moot because
161819 -         nobody has code to submit for Knowledge Management, under
161820 -         analysis on 030111. ref SDS 54 656G
161821 -
161823 -       ..
161824 -      Nobody Can Find Anything Project Specs Lost
161825 -      Specifications for OHS May Exist in Multiple Views
161826 -
161827 -      Follow up ref SDS 54 YN71.
161828 -
161829 - Eric says today...
161831 -       ..
161832 -      Reading my message, I see no reference to "misplaced". I know for
161833 -      sure that you never misplace anything! ref DRT 1 0001
161834 -
161835 -         Eric's letter on 030111 says "someone seems to have misplaced
161836 -         the OHS spec." and asks where did the spec go. ref SDS 54 YN71
161837 -
161838 -         This raises a question about what "spec" Eric is asking for
161839 -         help to find that is not listed in the record on 030111?
161840 -         ref SDS 54 C54O
161842 -          ..
161843 -         Finding the OHS spec and even remembering it is misplaced are
161844 -         of no great moment, and so raising an issue about accuracy in
161845 -         this instance reeks of "overkill" that is objectionable to
161846 -         people, noted by Murray Altheim's opprobrium on 020820.
161847 -         ref SDS 48 V66I
161849 -          ..
161850 -         Here, the example of failed memory illustrates a subsidiary
161851 -         matter that impacts productivity, because Eric is not alone.
161852 -         Many people are unable to remember information about
161853 -         specifications for more than a day or so, which occurs
161854 -         naturally in the mind as a result of intervening communication
161855 -         cycles, more commonly called information overload, explained
161856 -         in POIMS. ref OF 1 8774 and ref OF 1 0307  Since people are
161857 -         wired to remember th gist of the story, being made aware of
161858 -         failed memory seems like overkill in most all settings, i.e.,
161859 -         people are naturally defensive, because memory is a core
161860 -         competency.
161862 -          ..
161863 -         Eric noted in a letter on 011003 that productivity is
161864 -         paralyzed because people cannot find anything. ref SDS 39 EC5N
161865 -         Equally, devastating is failure to remember when something is
161866 -         missing, because people can only remember the gist of
161867 -         information using popular methods and technology. These two
161868 -         factors explain part of the cause for the downturn in the
161869 -         economy.  On 001207 Reuters reported experts saying that
161870 -         productivity and earnings fall because too many people are
161871 -         having too many problems. ref SDS 32 V54M  Failure to remember
161872 -         and inability to find information are often the genesis of
161873 -         problems.
161874 -
161875 -
161876 -
161877 -
1619 -

SUBJECTS
Knowledge Management Survey of Objectives, Accomplishments, Evaluatio
KM Failed to Meet Expectations 2 Generations Failed Need New Generati
Design KM Secret of SDS Because Progress Blocked by Innovation Loop D
SDS Utopia Compared to Using Other Popular Methods Because SDS Has Ev
Secret SDS Only KM Capability Breakthrough from IT Enables Steady Adv
Delayed Eric's Progress Doug Engelbart Cut Legs Out From Under Eric,
Knowledge Definition Not Understood, Eric Armstrong

4409 -
441001 -       ..
441002 -      KM Projects Failed to Meet Expectations
441003 -      Eric Can Advance KM by Reviewing POIMS and SDS Planned on 001126
441004 -
441005 -      Follow up ref SDS 54 YN77.
441006 -
441007 -      Eric does not discuss criteria for evaluating technology, which
441008 -      he raised in his letter on 030111. ref SDS 54 YN77
441010 -       ..
441011 -      Eric does not recognize in his letter today the advantage of
441012 -      adding a criteria for saving time and money, which was added to
441013 -      the list he submitted on 030111. ref SDS 54 MY3M
441014 -
441016 -  ..
441017 - Attribution Key Element of Knowledge Repository
441018 - Knowledge Management Implemented by OHS Difficult to Design and Build
441019 - SDS Meets OHS Objective to Augment Intelligence for Creating Knowledge
441020 -
441021 - Follow up ref SDS 54 GU9N.
441022 -
441023 - Eric says today....
441024 -
441025 -      Thanks for recognizing the work I did. I wish you had posted your
441026 -      response in fact -- except for one correction. Lee did copy my
441027 -      code as a basis, but he simplified it and spotted the source of
441028 -      the problems that I was too mired to see -- of course, he also
441029 -      left out some functionality, leaving that for a higher layer of
441030 -      implementation, but I'm willing to be convinced that was a good
441031 -      way to do it. ref DRT 1 RB5N
441033 -          ..
441034 -         Eric deserves a lot of credit for contributions to get the
441035 -         OHS/DKR effort launched, beginning on 000120. ref SDS 4 0001
441036 -         Throughout 2000 he was a primary source of ideas and for
441037 -         giving those ideas concrete form that enabled others to
441038 -         contribute meaningfully, illustrated by the specifications he
441039 -         submitted, listed on 030111. ref SDS 54 433K  There is no
441040 -         hesitancy to commend Eric's invaluable work, and in fact
441041 -         attribution was cited as an imporatant dimension of an
441042 -         effective Knowledge Repository, related by Eric's letter on
441043 -         000227 citing a presentation by Jim Sporer for Doug's
441044 -         colloquium at Stanford. ref SDS 6 0987
441046 -          ..
441047 -         It has not been effective to submit information to the OHS/DKR
441048 -         group because many object to SDS, illustrated by the record on
441049 -         020820, ref SDS 47 UV6G, citing an aversion to linking and
441050 -         accuracy, ref SDS 48 V66I, and to analysis, cited on 020823.
441051 -         ref SDS 50 R87J
441053 -          ..
441054 -         There is no objection to Eric citing references to SDS records
441055 -         in his correspondence with OHS/DKR folks, but experience shows
441056 -         that a developer should avoid self-promotion, noted by Jack
441057 -         Park, for example, on 011208, ref SDS 40 QF8M, under the long
441058 -         established rule that people believe the developer is not the
441059 -         best person to explain an invention, cited by Plato in his
441060 -         dialogs on Phaedrus, reviewed on 991209. ref SDS 2 3416
441061 -
441063 -       ..
441064 -      Doug Engelbart Has Not Delayed Work on OHS/DKR
441065 -      OHS/DKR Can be Implemented by People with Skills and Time
441066 -
441067 -      Follow up ref SDS 54 A35G.
441068 -
441069 - Eric says....
441070 -
441071 -      As for momentum, what I said was "should there be any ...". I
441072 -      agree with you that the whole effort was a non-starter. Right
441073 -      about the time I started to make some progress and get people to
441074 -      agree on a few basics, Doug cut my legs out from under me.
441075 -      ref DRT 1 RB6M
441077 -          ..
441078 -         Analysis on 020516 shows failure to produce code for Knowledge
441079 -         Management is caused by not understanding transformation from
441080 -         information to a culture of knowledge. ref SDS 42 M630  The
441081 -         OHS/DKR team made this point expressly on 000615. ref SDS 20
441082 -         6271
441084 -          ..
441085 -         On 001122 Eric reported that writing code to implement his
441086 -         specs for OHS/DKR was a complex problem that was difficult to
441087 -         solve. ref SDS 28 0001  This aligned with Eric's earlier
441088 -         report on 000503 that technology to support "knowledge" work
441089 -         is hard to understand. ref SDS 11 5033  On 001122 Eric did not
441090 -         mention Doug Engelbart delayed work by cutting the "legs out
441091 -         from under" anyone.  Earlier, on 000824 Eric reported Doug
441092 -         proposed the "Rod Welch" system for an OHS/DKR, ref SDS 21
441093 -         PU5N, and that Eric disagreed as related in the record on
441094 -         030111. ref SDS 54 A35G  Under this record, it is not clear
441095 -         why Eric cannot implement his own code in the same way that
441096 -         Jack Park is working on Nexist, reported on 010618.
441097 -         ref SDS 34 BP3K
441098 -
441100 -       ..
441101 -      Open Source Development Fractures Rather than Focuses Efforts
441102 -      Volunteers for Open Source Need Evidence of Potential Reward
441103 -
441104 -
441105 - Eric continues...
441106 -
441107 -      By and large, the group has remained fractured and splintered
441108 -      ever since. Eugene, bless his heart, listened to Doug too
441109 -      closely, so he tried to come up with a "system that lets everyone
441110 -      do their own pet projects and yet somehow nebulously everyone
441111 -      will interact". The failure proof for that scenario,
441112 -      unfortunately, is what we've witnessed. ref DRT 1 RB7J
441114 -          ..
441115 -         The need for focus was presented to the OHS/DKR team....
441116 -
441117 -           Offered chance to learn and
441118 -           develop KM......................... 000920, ref SDS 22 2V5F
441120 -            ..
441121 -           Explained why KM is difficult
441122 -           offered opportunity to improve
441123 -           to improve progress................ 001004, ref SDS 23 0001
441125 -            ..
441126 -           Offer to OHS/DKR group to learn
441127 -           KM in order to develop KM.......... 001102, ref SDS 26 0001
441129 -            ..
441130 -           Offer to make SDS available for
441131 -           learning KM........................ 001121, ref SDS 27 0001
441133 -          ..
441134 -         On 001126 Eugene Kim reported that people prefer to learn and
441135 -         perform KM using IT with greater diligence. ref SDS 29 QW8I
441137 -          ..
441138 -         Slow progress by OHS/DKR group is also occurring by others who
441139 -         are trying to advance from IT to Knowledge Management...
441140 -
441141 -              Microsoft    DARPA     Primus     Arthur Anderson
441142 -              Oracle       LANL      KMCI       Deloette & Touche
441143 -              Sun          SAIC      Intel      Booze Allen
441144 -              HP           DOD       Aerospace company
441145 -              IBM          Kanisa    Lockheed
441147 -          ..
441148 -         Everyone has failed to make progress, because KM is difficult
441149 -         to understand, and so requires investing time to study SDS,
441150 -         because SDS has proved to work, as reviewed on 030111.
441151 -         ref SDS 54 GU9N
441152 -
441153 -
441154 -
441155 -
441156 -
441157 -
4412 -

SUBJECTS
Busy Not Enough Time to Start Project at Sourceforge to Develop OHS/D
Busy Being Busy No Time to Save Time Money Learning SDS to Improve Wo

460401 -       ..
460402 -      Busy Not Enough Time to Invest to Develop OHS?DKR Project
460403 -
460404 -
460405 - Eric explains....
460407 -       ..
460408 -      I suspect that I really do need to start a project somewhere like
460409 -      sourceforge, and get some serious coders hammering away at it....
460410 -      ref DRT 1 RB7R
460412 -       ..
460413 -      But I'm kind of busy making a living, unfortunately. I'd love to
460414 -      have cycles to spend on this, even now.... ref DRT 1 RB8M
460415 -
460416 -         Eric expressed respect for the goal to develop technology for
460417 -         advancing beyond IT, during the meeting at SRI on 000324.
460418 -         ref SDS 7 FS3J
460420 -          ..
460421 -         Investing time to make a living leaves little time to focus on
460422 -         solving problems that make discovering the design for KM
460423 -         difficult, discussed above. ref SDS 0 SL90
460425 -          ..
460426 -         Eric might ask Jack Park how many "coders" are "hammering
460427 -         away" on Nexist.
460429 -          ..
460430 -         The threshold issue is to find a design that enables coders to
460431 -         make progress toward a viable result.  This is especially true
460432 -         for volunteers on an open source project.  If people are not
460433 -         being paid, they need a clear light at the end of the tunnel
460434 -         that illuminates imminent reward in return for expending
460435 -         effort, because everybody has to make a living.
460436 -
460437 -
460438 -
460439 -
460440 -
460441 -
460442 -
460443 -
460444 -
460445 -
460446 -
460447 -
460448 -
460449 -
460450 -
460451 -
460452 -
4605 -
Distribution. . . . See "CONTACTS"