Geoffrey Litt's Malleable Software Vision

Table of content
Geoffrey Litt's Malleable Software Vision

Geoffrey Litt is a design engineer and researcher who builds tools that let ordinary people customize their software. He did his PhD at MIT in human-computer interaction, advised by Daniel Jackson, with a thesis on building personal software with reactive databases. Before academia, he worked at Panorama Education building software for teachers.

Litt researches malleable software — computing environments where users adapt tools to their needs without engineering teams. He works at Notion after years at Ink & Switch, the independent research lab exploring the future of computing. See Malleable Software for the concept and its implications.

The Core Idea

From the Malleable Software essay (June 2025), co-authored with Josh Horowitz, Peter van Hardenberg, and Todd Matthews:

“The original promise of personal computing was a new kind of clay — a malleable material that users could reshape at will. Instead, we got appliances: built far away, sealed, unchangeable.”

The manifesto argues:

AI-Generated Tools

Litt’s December 2024 blog post describes an unusual AI use case:

“What’s unusual here is: the AI didn’t write a single line of my code. Instead, I used AI to build a custom debugger UI … which made it more fun for me to do the coding myself.”

While working on a Prolog interpreter, Litt hit tricky bugs in unification. Instead of having AI fix the bugs, he had it build a visualization tool to help him understand what was happening. The debugging became enjoyable rather than frustrating.

Background

PeriodWork
2019-2023PhD at MIT CSAIL — Programming interfaces
2020-2025Ink & Switch — Research on malleable software
2025-presentNotion — Design engineer

His PhD focused on end-user programming: how can ordinary people modify their software without learning traditional programming? His thesis, “Building Personal Software with Reactive Databases,” showed how spreadsheet-like techniques can let users customize web apps without writing code.

The Home Kitchen Metaphor

From the Dialectic podcast (June 2025):

“When I say malleable software, I do not mean only disposable software. The main thing I think about … is actually much closer to designing my interior space in my house. When I come home I don’t want everything to be rearranged. I want it to be the way it was. And if I want to move the furniture or put things on the wall, I want to have the right to do that.”

Malleable ≠ disposable. It’s about crafting an environment over time.

Ink & Switch Projects

The lab has produced influential prototypes. Litt worked on several of these directly:

The lab also pioneered local-first software, a set of principles for software that keeps data on your device while still enabling collaboration. Litt’s work connects these technical foundations to the user experience question: how do we actually give people control?

At Notion

Notion CEO Ivan Zhao has described the app as LEGO bricks — building blocks users combine freely. Litt’s research aligns with this vision. His role as design engineer bridges research insights with product reality.

AI’s Role (And Limits)

From the Malleable Software essay:

AI coding holds potential but isn’t sufficient alone. Problems:

The path forward requires both AI capabilities and new kinds of software architecture.

Litt writes about his own AI coding practice in “Code like a surgeon.” He uses AI for secondary tasks (writing documentation, spiking out changes, fixing clear bugs) but keeps primary design work hands-on. The goal: spend 100% of time on what matters.

Imbue Podcast (November 2025)

In Malleable Software and Human Agency, Litt discussed:

Core question: how can everyday people shape their software like clay so humans have more power and agency?

Key Insights

PrincipleImplication
Software should be clayUsers reshape tools to fit their lives
AI helps but isn’t enoughInfrastructure changes needed
Chef knife over avocado slicerGeneral tools beat specialized gadgets
Environment, not disposableCustomizations should persist and compound

Next: Armin Ronacher’s Agentic Coding Practice

Topics: ai-coding workflow open-source automation