About
I do my best work where engineering, interaction design, information design, and system clarity meet.
The current public direction is deliberately practical: local-first software, symbolic systems, editor/tooling thinking, and public surfaces that make the underlying structure visible.
Systems Register
I build systems
I have spent more than a decade building software across frontend systems, developer tooling, content platforms, and product architecture.
- Language tooling and parser-driven systems
- Interface architecture and design systems
- Developer experience and workflow design
- Accessible web applications and content surfaces
What I optimize for
I care about stable structure, readable files, coherent interfaces, and systems that stay understandable as they deepen.
- User experience design
- Software architecture
- User interface design
- Web content accessibility
Why Obsidian is relevant
Obsidian sits close to the problems I already care about: local-first trust, metadata-rich surfaces, extensible tooling, and the relationship between structure and interaction.
- Local-first architecture matches how I think about ownership and user trust.
- Editor, plugin, and metadata-heavy systems are exactly where I like to work.
- Small teams with strong product taste are where I can contribute most effectively.
Art as product sensibility
My art practice informs how I think about rhythm, symbols, pacing, surface coherence, and the feeling of a tool.
I do not separate design from systems work. The structure is part of the interaction.
Surface Register
Current engineering presence
Long-form storytelling
Compressed surfaces
Current Direction
I am aligning my public work toward a durable throughline: plain-text systems, richer syntax, interactive codeblocks, projection surfaces, and software that stays legible to the people who use it.
That is the connective tissue between Spw, the site overhaul, and my interest in Obsidian.