Work / Noize · 2026
adeyy
One short link, one QR code, and the ability to change where they point long after the menu has gone to print.
The problem
A café prints a QR code on two thousand table cards pointing at a winter menu. Spring arrives. The cards are landfill — unless the code was never bound to the destination in the first place.
What I built
Indirection, essentially: the printed code resolves to a record, and the record decides where you go. Change the record, every printed artefact updates instantly.
The redirect is the product, so it has to be genuinely fast and genuinely always up. Resolution is cached in Redis at the edge and the hot path does no database round trip — a scan resolves before the phone camera has finished dismissing its own overlay.
Free to create links, a dollar per active code per month. Pricing that only charges for codes actually in the wild.
What it came to
- Re-pointable
- After print, after distribution
- Edge-cached
- Redis resolution, no DB on hot path
- 1 link
- Short URL and QR from one record
- TypeScript
- React
- Firebase
- Cloud Run
- Redis
Open to senior engineering roles
Tell me what you are building.
Full-time roles, contract work, or a system that needs someone to own it. I read everything and reply within a few hours.