Location: Seattle, WA
Remote: preferred
Willing to relocate: no
Technologies: TypeScript, Python, React, Next.js, Django, Postgres
Resume: upon request
Email: exogen@gmail.com
Your classic web and open source hacker with over 20 years of experience, most fluent in JS/TS and Python. I've tackled a wide variety of interesting problems and domains, e.g. graph isomorphism, query expansion, geocoding, dev tools, performance, data visualization, API design, server-side rendering, entity matching/record linkage, web scraping, games, reverse engineering binary formats, typography, codebase migrations, and more. Both startup and big-corp experience, but I prefer working with small teams.Ask me about the time a stolen bike led to creating an arbitrary-precision math library and discovering a bug in Mathemetica...
(Aside from that: not a fan, it makes the chrome of the video player more distracting.)
I’m out of the loop - what happened with Apple’s Photos app? I’ve seen their marketing from announcements earlier in the year and was looking forward to the update - is it underwhelming?
ca. 2017 I undertook the considerable task of building a GraphQL interface to MusicBrainz, to support a side project of mine. This was a great experience for learning the breadth of MusicBrainz and how to design things with GraphQL. Sometimes I look at the documentation generated from the resulting schema and wonder when I ever had that much time: https://github.com/exogen/graphbrainz/blob/master/docs/types...
Or a more complicated app: https://exogen.github.io/t2-model-skinner/
Are all of Next.js’ features overkill for such sites? Sure, but the convenience such frameworks provide is worth it. And the reason to prefer it over something like Vite is simply routing, which Vite doesn’t cover out of the box, so as soon as I want to add a second page, I now have another problem to solve.
Next.js’ best feature is simply that you’re up and running with `npm i react react-dom next` and step two is just writing the pages.