Recurring themes in presentations and discussion in the hallway during
ILC-2005:
- Keep the source code with the binary and version both
- Annotate code and define execution environments
- Make patching live systems reversible and keep track of all changes
- Code comprehension. Create programs that understand programs. Maybe teach CYC about programs and programming and let it read it's own code
- Code verification and correctness proofs
I'm totally convinced that, if we don't get at least engineering AI (as defined by Drexler) or usable program verification/proofs, the complexity of our systems will eventually
make maintenance impossible.
I picked up some books while browsing book stores in San Francisco:
Reading the above list I'm ready to agree with Erik Naggum, who wrote about book stores in a posting to c.l.l.:
I just bought a book on a hunch the other day while trying to get out of
the magic spell that bookstores seem to cast on me, robbing me of my free
will and causing me to buy books for no good reason. I should have all
my credit cards say "not valid in bookstores unless holder is accompanied
by a responsible person".
I've updated the link to my
US t-shirt shop.
There were some requests for Polo shirts at ILC05. I've added a black Polo shirt with LISP lettering on the front side and a cons cell on the back. Suggestions for other designs are always welcome.