Overview
What I build and how I work.
Who Zac is as a developer
I work best on product surfaces with visible behavior: tools, dashboards, maps, GitHub Pages sites, and automations where the underlying process matters as much as the interface.
What I like building
My strongest projects connect real user actions to working software: field asset maps, Twitch/OBS automation, public-domain movie voting, browser canvas drawing, and small interactive tools.
Current technical focus
- Python automation with explicit recovery paths
- Frontend/browser tools with readable state
- Map-based field interfaces
- Canvas tools, games, and touch input
- Case studies that explain engineering tradeoffs
Project approach
I start with the user path, build the smallest useful version, then tighten navigation, state, empty screens, keyboard behavior, mobile layout, deployment notes, and honest production risks.