miniblog.

← Back to all posts
Jan 28, 2013 at 16:09
The difference between a good tool and a bad tool is that the critics of a good tool are its users.

Related Posts

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 17, 2026 at 10:06
I'm adding uptime data to my personal LLM bot. Does this information belong in the system prompt? That was my initial plan, but I'm thinking that a tool would be better. Tools let me see information provenance ("queried the uptime tool"). There's also a small caching benefit.
Mar 15, 2026 at 20:42
Really elegant developer tool: Go's inline IDE feature is used with deprecation markers, so call sites are autofixed from OldApi() to NewApi() based on the implementation of OldApi.
//go:fix inline and the source-level inliner - The Go Programming Language
How Go 1.26's source-level inliner works, and how it can help you with self-service API migrations.