(01)personal project

EATS

A restaurant finder I've rebuilt three times. Still not done.

EATS

Three versions over three years. The first one during bootcamp: Rails backend, React frontend, barely worked. The second one was me proving I understood separation of concerns. I did. It was over-engineered.

The third is the one that's live. Next.js, Supabase, Clerk. Yelp API under the hood. It does one thing: surfaces places worth going without making you scroll through a hundred generic results first.

Versions

Bootcamp was Rails plus React. I learned the shape of full-stack there, not polish. Round two split frontend and backend on purpose: cleaner boundaries, more machinery than the product needed. The stack that ships now is the one I wrote when I stopped proving concepts and started trying to finish.

Live

Auth is Clerk. Data lives in Postgres through Supabase. Tailwind for layout. Deployed on Vercel. None of that is the point. The point is the loop: search, save, come back. The arc of this project is the arc of how I learned to build. Each version matches how I was thinking that year. That's either embarrassing or honest. Probably both.