Skip to content

Book a call

Eugene, Oregon · one person, whole builds

Tagged

Studio

4 posts on studio.

Trained to listen: where my engineering judgment comes from

The nine posts before this one are about code. This one is about where the judgment underneath them came from: a house of two immigrant engineers, junior tennis, recovery in 2014, a decade of intake, assessment and crisis work, and what all of it does to the way I build.

The tool bench a one-person studio builds for itself

A private bench of ten apps, no accounts, no servers, nobody to support. Here is what is on it, how the slide proofer works out where a platform will crop before the file leaves my hands, and what happened when I ran a slide I had already posted through my own guides.

Two kids built games, so I gave games a content type

Lulu is 10, Otto is 11, and they are my niece and nephew. Over a handful of afternoons this summer they finished three browser games they wanted to play, and I had to decide where those games would live on my site. Three hand-written pages would have rotted by autumn, so games became a content type instead: a table, a folder scan, and a page that ends with what the game taught the kid who made it.

The baton passes

Why a new software studio in Eugene, Oregon is named after a man who spent forty years moving packets.

studio
story

← All insights