About
I mostly build tools for maps, routes, and other messy datasets.
The work is usually frontend-heavy, but the real job is making a system easier to inspect.
What I care about
If the structure is hard to read, the tool is failing.
I like interfaces that help someone answer a real question. A map, a few filters, a panel, and a search box can do a lot if they are arranged properly.
I would rather make a tool feel obvious than clever.
Why transport
Transport keeps producing good interface problems.
Routes, stops, timetables, service changes, and reachability all interact, so the interface has to explain a system rather than a single object.
That is the sort of problem I enjoy most.
Technical background
Mostly JavaScript and TypeScript, with Python and SQL close behind.
Most of the portfolio is browser-based, but a lot of the work starts with data wrangling, geospatial analysis, or small bits of tooling around the interface.
I also have some research exposure, including machine learning, NLP, and collaborative nnU-Net work on kidney CT segmentation with researchers at Memorial Sloan Kettering Cancer Center.