about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2018-07-19 12:18:37 -0700
committerKartik Agaram <vc@akkartik.com>2018-07-19 12:18:37 -0700
commitd20684d6b8e2f1a271ea58558881f2c86a83ac06 (patch)
tree2f14a5f5b532d3ad566768af2c6b06f2037f2242
parent4a3a616e71673419f2b21c8dd2c0cb1d4346a8b0 (diff)
downloadmu-d20684d6b8e2f1a271ea58558881f2c86a83ac06.tar.gz
4369
-rw-r--r--subx/Readme.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/subx/Readme.md b/subx/Readme.md
index 5e58917e..2d2031cd 100644
--- a/subx/Readme.md
+++ b/subx/Readme.md
@@ -9,11 +9,11 @@ and libc.)
 
 1. It seems wrong-headed that our computers look polished but are plagued by
    foundational problems of security and reliability. I'd like to learn to
-   walk before I try to run, use the computer only to check my program for
-   errors rather than to hide low-level details. This approach adds to the
-   burden of the programmer, but may make the hard problems more tractable.
-   We can always add HLLs back once the foundations are redone, but it seems
-   valuable to not require a HLL to build the foundations.
+   walk before I try to run. The plan: start out using the computer only to
+   check my program for errors rather than to hide low-level details. Force
+   myself to think about security by living with raw machine code for a while.
+   Reintroduce high level languages only after confidence is regained in the
+   foundations. Delegate only when I can verify with confidence.
 
 2. The software in our computers has grown incomprehensible. Nobody
    understands it all, not even experts. Even simple programs written by a