Local-first software
Tools feel different when ownership, privacy, and offline use are properties of the architecture rather than promises in a policy.
Notes
Interests
Ideas I keep coming back to, and why. Shorter and less finished than the project write-ups.
Systems that explain themselves
I’m drawn to software whose boundaries, failure modes, and tradeoffs remain visible to the people who build and use it.
Rust
A language that makes resource ownership and system boundaries explicit, and rewards careful design.
Data made explorable
A good interface lets people ask their own questions of a dataset instead of prescribing a single conclusion.
Hardware and audio
Physical systems make software constraints tangible: timing becomes audible, interfaces become tactile, and abstractions meet the bench.