- notably Smalltalk and Plan9 - a "system" not a "language"
- some lose ideas:
- if we have a system that captures what functions are called with and surfaces it to the user, then types are not necessary, since we can rely on what kinds of things the system operates on in real use
- any sort of static analysis is not necessary, since if writing code interacts with actual "living" things, they can just be "asked" what do they expose
- if the system is connected to production use, extra debug visualizations (for Solving Things Visually) could provide information like - how "hot" this code-path is, what kinds of things this errors on, etc.
- 2026-01-05Independent Consulting, and Interfacing with LLMs1
- 2025-10-13Open Questions Around LLM Interfaces1
- 2024-09-05Replit Agent — IDE for Humans and LLMs2
- 2024-05-17Live-Programming Issues1
- 2022-10-03Strange Loop, and research at Glide1