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: December 19, 2007 07:11 PM Wednesday; Rod Welch

Gary submitted analysis of SDS criteria for Windows application.

1...Summary/Objective
2...Transformation SDS Steady Exposure Relentless Pressure Good Practice
3...Moving from DOS to Windows Tricky Maintain Response Usability


..............
Click here to comment!

CONTACTS 

SUBJECTS
Meeting Notes 071213 Telecon SDS Windows Application Design Record M

0803 -
0803 -    ..
0804 - Summary/Objective
0805 -
080501 - Follow up ref SDS 21 0000.
080502 -
080503 -
080504 -
080505 -
080506 -
080507 -
080509 -  ..
0806 -
0807 -
0808 - Progress
0809 -
080901 - Transformation SDS Steady Exposure Relentless Pressure Good Practice
080902 -
080903 - Received a letter from Gary with copies to Morris and to Jack Park,
080904 - and which incorporated his SDS record reporting the telecon with
080905 - Morris on 071212. ref SDS 21 WD8J
080907 -  ..
080908 - For some reason the "Subject:" of Gary's letter refers to "Open
080909 - standards and open source," which is not mentioned in the letter.
080910 - This is part of entropy that degrades order in the record cited by
080911 - Jack Park on 010908. ref SDS 11 UV4H  Entropy degrading management
080912 - productivity toward confusion and failure was reported in the USAFIT
080913 - study, reviewed on 970707. ref SDS 5 0611
080915 -  ..
080916 - On 001126 Eugene Kim proposed using diligence to apply existing
080917 - Microsoft technology, ref SDS 9 4E3X, rather than learning Knowledge
080918 - Management by using SDS. ref SDS 9 QW8I  Eugene's point 6 proposed
080919 - conforming subject fields to document content. ref SDS 9 M36R
080920 -
080921 -     [On 071222 Morris used the same subject to ask about SDS essential
080922 -     features. ref SDS 22 PX5H
080924 -      ..
080925 -     [On 080108 post script recommends conforming "subject" of
080926 -     documents to the content. ref SDS 23 WX7Q
080928 -  ..
080929 - Gary's effort today incorporating SDS records into email demonstrates
080930 - deliverables of Communication Metrics to an engineer attempting to
080931 - develop a new version of SDS.  On 071212 Morris asked for an
080932 - explanation of "SDS records," rather than examine records to correlate
080933 - explanation with experience. ref SDS 21 KO4F  Gary has noted
080934 - previously the need for persistant exposure that helps transform
080935 - "funny" ideas in the proposal to NSF on SDS tools for good management,
080936 - noted by Morris' colleague at Intel on 990713, ref SDS 8 1767, and
080937 - further converts support to "work intelligently" that seems "alien"
080938 - and "foreign," noted by another Intel colleague at that time,
080939 - ref SDS 8 2150, into useful, productive, and enlightened capabilities.
080940 - Transforming perceptions of "crummy" into "good" ideas has been a
080941 - longstanding issue in high tech, reported on 960612. ref SDS 3 1368
080942 - It took a long time for Intel management to recognize that
080943 - microprocessors Intel developed were useful, reported on 960304.
080944 - ref SDS 2 245H
080946 -  ..
080947 - Putting SDS records in email supports Morris' recent objection to
080948 - links, renewing complaints on 990712, ref SDS 7 5837, about uniform
080949 - distribution of precision access to everything in the right place at
080950 - the right time.  Links in SDS records on 980405, ref SDS 6 3990,
080951 - solved Morris earlier objection on 960721 that there was no access to
080952 - links in printed SDS records. ref SDS 4 3230
080954 -  ..
080955 - On 010425 Morris described self-evident benefits of timely access as a
080956 - "utopia" compared to other methods. ref SDS 10 EP7F  This was echoed a
080957 - few months ago on 071006 by Paula at Kaiser, who described instant
080958 - access in SDS as "amazing" compared to Knowledge Management tools at
080959 - Kaiser. ref SDS 18 Q969  On 071126 Paula reported continuing failure to
080960 - obtain information for her work from Kaiser and from UCSF, and got
080961 - what was needed from clicking linsk in SDS. ref SDS 20 TH8L
080963 -  ..
080964 - Despite advantages of speed and precision, in the past year Morris has
080965 - given up on links, at least for SDS.  He recently tried clicking links
080966 - Gary provided on tools to document SDS development, and was
080967 - discouraged that links in that case failed.
080969 -  ..
080970 - Maintaining exposure to SDS records empowers people to discover in
080971 - their own time benefits of connecting cause and effect that yields the
080972 - power of knowledge, reported on 040312 citing the "locality principle"
080973 - presenting a scientific explanation of "knowledge." ref SDS 16 YH4G
080974 - Strategy helping people transform work practices to implement the
080975 - power of knowledge was related on 040102 reviewing Gary's work with
080976 - SDS during 2003. ref SDS 15 WI3H  Gary cited this strategy on 030504.
080977 - ref SDS 13 9X62  He followed up on 031211 with research on a theory of
080978 - continuous exposure to changes attitudes toward good management like
080979 - relentless pressure changes the landscape of geology. ref SDS 14 PE5Y
080980 - This supplemented Gary's powerful letter on 011210 explaining
080981 - persistence is essential to help people improve. ref SDS 12 R66K
080983 -  ..
080984 - Curiously, links in the SDS record Summary are not active.  This gives
080985 - the appearance of SDS but stripped of power and speed.  Clicking on
080986 - links goes nowhere, and so is misleading.  This presents an oddity of
080987 - working on a project which has a primary aim of making links fast and
080988 - easy to apply the power of knowledge, yet delivering links that don't
080989 - work to a person who objects to linking,
080990 -
080991 -
080992 -
080994 -  ..
080995 - Moving from DOS to Windows Tricky Maintain Response Usability
080996 -
080997 - Gary explains challenge migrating efficient DOS technologies into
080998 - Windows applications without degrading usability essential for
080999 - productivity, discussed with Morris on 071212. ref SDS 21 IF4I  He
081000 - reports that Wordperfect took several iterations, and Maxthink
081001 - efficient usability was difficult to deliver in a Windows application.
081002 - Gary says today in part...
081003 -
081004 -       The MaxThink outliner in DOS is a very nice tool.  In Windows it
081005 -       is a dog, even though, nominally, the interface is identical (it
081006 -       isn't quite).  Also, the new files are no longer plain text, so
081007 -       no processing of them is really feasible, which is not good.
081009 -  ..
081010 - This aligns with Gary's letter on 041111. ref SDS 17 OL9F
081012 -  ..
081013 - Goals for integrated, ergonomic design to increase productivity was
081014 - considered during the meeting on 071113 citing Mike Poremba's report
081015 - on SDS responsiveness and efficient usability that he found is not
081016 - available in Windows applications. ref SDS 19 V45N
081018 -  ..
081019 - Would be easier to complete this record with access to construct
081020 - connections into Gary's actual record.
081022 -  ..
081023 - Gary discusses Morris' planning to design records with flexible fields
081024 - and without using line numbers to identify field types from the
081025 - discussion on 071212. ref SDS 21 GI9I  Gary says in part at line
081026 - 060752...
081027 -
081028 -        Morris envisions a single data structure that is a hierarchy of
081029 -        elements with each element having an arbitrary set of tags.
081030 -
081031 -            Essentially each element has a set of tags as a template
081032 -            and an instance has tag - value pairs.
081034 -  ..
081035 - Gary explains at line 060761 Morris' proposal on 071212 to combine
081036 - work product with program code loaded into memory, similar to email
081037 - parograms. ref SDS 21 058J  Gary says in part beginning at line
081038 - 060761....
081039 -
081040 -        Morris wants to keep the entire data structure in memory
081041 -        rather than managing disk access.  This approach will certainly
081042 -        simplify the initial implementation.
081043 -
081044 -           [On 071222 Morris commented that putting everything in
081045 -           memory may be a problem. ref SDS 22 TM6U
081047 -  ..
081048 - Gary addresses Morris' request on 071212 for an explanation of an SDS
081049 - "record." ref SDS 21 KO4F  At that time on 071212, ref SDS 21 863H,
081050 - cited prior work on 890523 explaining flexible structure. ref SDS 1
081051 - P13O  Complementarity between SDS structures and functions was also
081052 - cited from work on 890523. ref SDS 1 LV59
081054 -  ..
081055 - Gary says in part at line 060803...
081056 -
081057 -        An SDS Record is a user-defined unit of information that
081058 -        represents an event, idea, thought process, or other focused
081059 -        activity.
081060 -
081061 -             [On 071222 Morris requests essential SDS features.
081062 -             ref SDS 22 3V35
081064 -              ..
081065 -             [On 071222 functions for SDS features are explained.
081066 -             ref SDS 22 6P9J
081068 -              ..
081069 -             [On 071222 Gary describes SDS record identification and
081070 -             explains 7 essential features. ref SDS 22 PA6P
081072 -         ..
081073 -        An SDS record is identified to the system by a user id and a
081074 -        creation timestamp to the second.  The Schedule and Diary are
081075 -        presented sorted by the timestamp.
081076 -                     ..
081077 -               ..
081078 -        An SDS Record has a user-supplied title that allows human
081079 -        recognition of a specific record within the time-ordered index.
081080 -
081081 -
081082 -
081083 -
081084 -
081085 -
081086 -
081087 -
081088 -
0811 -