Why this page exists
Some visitors want the work before the biography. This is the shortest path if you would rather look at systems, runtime choices, and shipped artifacts than read a general introduction first.
This page is the project index for what is actually visible here. Not a padded case-study wall, not a disguised resume. Just the systems, experiments, and experience layers on this site that are public enough to inspect and specific enough to mean something.
Some visitors want the work before the biography. This is the shortest path if you would rather look at systems, runtime choices, and shipped artifacts than read a general introduction first.
Not every useful thing I have worked on can be public. So this page focuses on the live and inspectable work already visible on the site instead of pretending public equals complete.
These are the pieces that most clearly show how I think: performance-first delivery, readable interfaces, restrained data handling, and enough visual personality that the result still feels alive. Each card now opens into a fuller case-study page instead of stopping at the index.
A 3D globe that turns recent visits into ambient presence instead of analytics theater.
Poster-first loading, live and history modes, approximate geolocation, and a deliberately short memory window so the experience feels alive without feeling invasive.
The broader personal site system: static-first, searchable, and public-safe by design.
A fast Astro-based site with deliberate navigation, clear content lanes, and pages like About, Work, Uses, and Elsewhere that keep the person visible without oversharing.
Search, resume reading, and sharing tools that help a quiet site stay usable.
A custom search index, keyboard-first search overlay, reading progress persistence, resume reading prompts, and small reader utilities that stay helpful without turning into dashboard chrome.
A light edge data path that keeps the globe current without building a long-term reader profile.
Pages Functions forward approximate visitor beacons to a Durable Object, which keeps rolling snapshots and history for the globe while staying intentionally restrained about retention and identity.
A system still has to be understandable, maintainable, and calm to operate. Performance only gets more meaningful when the rest of the shape is clean too.
The point is not only to ship a thing. It is also to leave behind enough explanation that another person can understand why it looks and behaves the way it does.
I like systems that stay disciplined without becoming sterile. A little visual taste and warmth makes software easier to remember and easier to trust.
Why this blog starts with Astro, a deliberate WebGL island, and a bias toward edge-readable systems.
Treating hydration as a design constraint leads to cleaner reading experiences and a healthier performance budget.
Fast interfaces shape user confidence before anyone notices architecture, reliability charts, or clever implementation details.