An RSS Feed Nobody Could Find

A brainstorm for new site features produced a shortlist, and "add an RSS feed" sat near the top — reasonable, cheap, and clearly missing. It wasn't missing. /rss.xml had shipped months earlier, in the same PR that added posts, and had been serving valid feed XML the entire time. The actual gap was narrower and less interesting to pitch: nothing on the site pointed to it.

Where the assumption came from

The idea reads as plausible from the outside — a personal blog without a feed is a common gap, and nothing in the visible UI (no icon, no link in the footer) contradicted that read. The mistake wasn't proposing the feature; it was proposing it without first grepping the codebase for rss, which would have surfaced the route in seconds and changed the whole shape of the task.

What "ship an RSS feed" turned into

Once the real gap was clear, the fix was two small additions: a <link rel="alternate" type="application/rss+xml"> tag in the root layout so feed readers and browsers can auto-discover it, and a visible "RSS" link in the footer next to GitHub and LinkedIn. Total diff: a few lines, not a new route, not a new dependency.

The actual lesson

"This looks unbuilt" and "this is unbuilt" are different claims, and only one of them is checkable in under a minute. A brainstorm is a good source of direction and a bad source of ground truth — the fix for that isn't skipping brainstorms, it's treating every item on the list as a hypothesis about the codebase, not a fact about it, until something has actually gone and looked.