writing

The orange binder

· 1 min · ~400 token

As a kid I filled a binder with robots I never built. Today I build my ideas, and I keep the ones that stopped too.

As a kid I wanted to be a mad scientist, and I meant it. I spent my afternoons filling an orange binder with projects: robots of every shape, complicated machines, unlikely inventions. I dreamed of buying an Ape Car, the tiny Italian three-wheeler, and turning it into a mobile lab.

Drawings of robots like Triangolix and Volix

None of those robots ever left the page. I built with LEGO and took apart any device I could get my hands on, to see how it worked inside. Putting it back together, most of the time, I could not.

The binder did one thing right, though: it kept everything. The ideas that worked and the ones left halfway sat in the same place, one after the other.

The tools are here now

Today the AI writes the code. I design the architecture, prepare the context the agent works in, check and ship. The distance between an idea and something that actually runs has shrunk enormously, so the ideas that used to stay on paper now become projects.

Many are born, and not all of them reach the end. That is fine, as long as I do not lose them.

The grown-up binder

This site does the binder’s job. The projects page has all of them, each with its real status: in progress, the tools I use every day, ideas on hold, archived.

And every project carries the attempts that came before it. Nexus, where I keep my tasks, notes and data today, came after quite a line of others:

Where Nexus comes from
  1. 2024 Plannerinator
  2. 2025 Verbosa
  3. 2026 NanoClaw
  4. 2026 Life Terminal
  5. 2026 Almanac
  6. 2026 Nexus in Elixir
  7. 2026 Bob
  8. 2026 Nexus

Its page also tells what each one left to the next.

How I work with agents is in the method. The Ape Car, on the other hand, is still in the binder.

Related writing