Programming the Logic Theory Machine

▲

The lines he pulled

“A superabundance of information and alternatives is provided, but with no known clean-cut way of proceeding to a solution. These situations require ‘problem-solving’ activity.”

p.230 · underlined before the first coffee of the read

“No one way of proceeding ensures solution of a given logic problem, and hence, many alternative subroutines exist.”

p.231 · boxed, with “the casting of a wide net” beside it

“The programmer should be able to specify any process in whatever way occurs naturally to him in the context of the problem.”

p.231 · the flexibility requirement, boxed whole

“There is no erasing problem in the working memory, since working memory elements are erased automatically when a subroutine has been carried out.”

p.237 · answered in the margin with two words: /clear command

●

The read, page by page

pp.230–31

BThe casting of a wide net. — at the many-alternative-subroutines passage; the paper's whole philosophy in five words.
AA starting point for processing the big issues quicker. — at LT's non-numerical character.

p.232

BVs. Claude: publicly facing, development by Anthropic (somewhat) — out in the open for the public. — at the Fig. 1 logic element, with an “Oh. yeah” and a smiley beside the key.
AHow fast is this relative to today? — under the JOHNNIAC footnote: 15,000 operations per second.

p.233

ASort of like a DNA or peptide strand. — at the method of detachment.
ELike a congo line. — at the location words, each one holding the address of the next.

p.234

BI envision this like the wood slot that holds your Scrabble pieces as they come out of the bag and on to the board. — the available-space list, named for life.
ALike white-out, almost. — deletion by cutting the location word.

pp.235–36

AWould this be like a paper title and thesis, then the subheadings and partitions that embody the argument? — the routine hierarchy read as a piece of writing.
CThe “delete/wipe” we talked about in the other reading that you can always go back to — e.g. mirrored on to SSD. — list memory vs working memory, mapped onto his own archive.
DSpelunking a sample before diving in fully. — find-and-store searching a list with tests.

p.237

GA receipt of job, if you will. — the trace as the prime source of data; 1957 tracing read as a receipts system.
HHelps to spot and diagnose where time might be spent unwisely, or where the whole program could be refined. — the tallies.

pp.238–39

FSwapping custom-built exactitudes for the crutch of a set of common locations, assuming that most programmers would benefit from the latter. — the gist of variable references, in one coined word.
CLike a run of the subroutine bundles, logged, that does not tamper with the master template. — self-modification handled by lists; runs log, the master stays sacred.

p.240

★Today people ironically hardly even know what that — the founding basis for how we prompt — is. — at IPL's “provincialism,” the last margin before the seal.

Structure is scaffold; every quoted line is his, verbatim from the annotated pages. A handful of margin reads remain garble-flagged in the decode and are excluded or trimmed here rather than guessed at.

No one way of proceeding ensures solution of a given logic problem.A. Newell & J. C. Shaw · Programming the Logic Theory Machine · 1957 Western Computer Proceedings

Where the margins reached

The lines he pulled

The read, page by page