I’m from the generation that still complains about the death of Google Reader. So when I had some surprising quick wins using AI at work this week — wins that genuinely convinced me I could just crank something out in an evening — I decided to spend my Friday night building my own RSS reader.
The result is cloud-reader, running entirely on the Cloudflare developer platform. You can see the live deployment at cloud-reader.alexcostaviana.workers.dev — though I may put it behind Cloudflare Access at some point.
The stack is all Cloudflare under the hood: a Worker for the REST API, D1 (SQLite) for storage, and static assets — all in a single deployment. On top of that: Hono for routing, Drizzle ORM, React 19 + Vite for the frontend, and Cloudflare’s Kumo UI components with Tailwind v4.
I used the same agents + worklog approach I’ve been developing on this blog. Every decision and dead end goes into a WORKLOG.md, which makes it easy to reload context between sessions without losing continuity. I also broke the project into explicit milestones — and the milestones weren’t about managing complexity, they were about protecting space at the beginning to carefully think through architecture and design decisions. Things like migration strategy, linting setup, and tool choices. Getting those right up front meant the project moved faster once it had some maturity, not slower.
Like I posted on Twitter: in about two hours I had 60+ commits — tested, linted, type-checked, and documented. I feel like I’m living in the future and way behind everyone at the same time.