miniblog.

← Back to all posts
Mar 15, 2024 at 15:28
The lisp model of programming is generally: write a function, evaluate it, interactively call it with some arguments, iterate. Jupyter notebooks are similar. Why not automatically evaluate definitions (not expressions) whilst working? It seems like it could be a satisfying way to work with code.

Related Posts

May 27, 2026 at 21:28
25
I'm writing a Path type in my programming language but not sure what methods belong on a Path. Should I have some_path.read_string() or fs::read_string(some_path) instead? I love .method() for IDE completion, but I don't want Path to be cluttered. I'm also trying to avoid UFCS.
Mar 20, 2026 at 12:02
223
Excellent series on Self, both the programming model and the tool chain. I love how opening an inspector on a value (e.g. nil) then shows a link to all occurrences of the value in other open inspectors!
Environment and the programming language Self (part one; environment)
Environment and the programming language Self (part one; environment)
I bring you a message about a language that has been at the birth of many others, but almost no one knows it. A rumor of a graphical environment offering options like no other, but almost no one using it. I also bring information about a virtual machine supporting reflection almost to infinity, reaching almost half of the operating power of C in numerical calculations in its time, yet today forgotten.
Mar 7, 2026 at 17:18
3
Agentic programming workflows rather remind me of genetic programming. The agent has a validation step that looks like a fitness function, and both run iterative trials.