Rebooting This Site

For a few years dustinmorgan.org was a three.js scene. It had a spinning DNA helix, a textured moon, and five thousand stars flying past as you scrolled, with my life story floating on top. I built it to learn three.js, wrote the bio in one sitting, and never touched it again.

It didn’t work on a phone. It loaded a WebGL scene, two CSS frameworks, and a reCAPTCHA script nobody used, all to show a few paragraphs. And the bio was mostly old hacker stories. It said nothing about what I actually do now.

So I rebuilt it. It’s static pages generated by Hugo, and it works on a phone. There’s an RSS feed. I’m still an engineer at heart, so the home page kept a little three.js: a helix of signals running across the top. It only runs on the home page, it stops when you scroll past it, and the site works fine without it.

What it’s for

I want this to be an honest record. If you look me up, you should find what I’ve built, what I’m building, and what I measured, warts included.

Most of my time outside work goes into how language models remember things: continual learning, long-context memory, and making both cheap enough to run on GPUs people actually own. The public pieces are on GitHub. Most of the active work is private for now, and I’ll write about it here as it’s ready.

The rules

• Numbers come with the setup. If I quote a benchmark, you get the hardware, the settings, and what the comparison left out. I’ve already had to walk one back (I owe PyTorch a fair fight), and then a whole format (What I got wrong about SQ4).
• Failures get posts too. Regressions, dead ends, and what caused them.
• No vaporware. I won’t write about things that don’t exist yet like they do.

The posts from April and May first ran on a TensorWire dev blog. I moved them here, so this is the only place I write now.