Durable tools
Products should remain legible and maintainable over time, not collapse under their own complexity.
About
I build software that stays useful beyond the first launch.
I care about clarity, durability, and practical usefulness. Most of my work sits where calm software, local-first thinking, and real-world workflows meet.
What I build toward
Calm interfaces
I prefer software that feels composed and trustworthy, with hierarchy doing the work instead of visual noise.
Local-first systems
When reliability and privacy matter, offline-friendly behavior and local data handling are default choices.
Purposeful experiments
Exploration matters, but each experiment should point toward practical output and a better shipped surface.
How I work
- Small stack bias: plain web foundations and lightweight scripts before heavy tooling.
- Shipping rhythm: iterate in small steps with visible results, then refine based on real use.
- Honest systems: clear defaults, graceful failure modes, and update paths that stay understandable.
- Long arc thinking: each project should contribute to a coherent body of work over years, not weeks.
Long-term direction
I am building across software products, AI-assisted systems, and practical reference tools, while moving toward a stronger bridge between digital workflows and physical-world making. The goal is not volume. The goal is a durable catalog of useful work with a clear point of view.