Jay Griffin

About

A bit about how I got here, plus questions I get asked and a few I ask myself.

Background

I've been living inside computers since I was five — Paint and Pinball first, then PC gaming, modding, running game servers, building machines from parts, and reinstalling Linux more times than I can count. By the time I wrote a line of code I was already comfortable with filesystems, config files, and the command line. I just didn't know yet that being unafraid of the machine was most of the battle.

The click came from AutoHotkey. I wanted one hotkey that opened the five websites I checked every morning. It worked — and then I realized the list could just as easily be a hundred. That's the whole idea of a program: write the instructions once, and the machine runs them instantly, perfectly, every time.

Everything since has been self-taught and problem-first. I learn by building something I want to exist, getting it working end to end, and writing down what I figured out along the way. These days that means full-stack TypeScript, a database, an LLM somewhere in the loop, and a deployed URL at the end of it — the whole setup is in my stack.

About five years of writing code in, the shape of it is clear: backend and full-stack, on the web, with a preference for owning the whole path from schema to deployed URL. I'm not a designer and I'm a genuinely terrible artist, but I think UI and UX matter enormously — I just get there by studying patterns that already work and iterating on them rather than drawing something beautiful from a blank canvas. The one-page version of all this is on my resume.

I work with AI agents daily and I'm opinionated about how. They're very good at execution and still need someone holding the architecture. I write down decisions as I make them — why a format was chosen, why an approach failed — which is partly how I learn and partly so the reasoning survives past the moment.

Away from the keyboard I collect Rubik's cubes, and I hike, bike, run, and lift. I track most of it, which is where a lot of my projects actually come from — Food Math exists because I wanted a faster way to log what I ate, not because I set out to build a nutrition app. Most of what I build starts as something I wanted to use.

About me

About this site

Something not answered here? Get in touch.