The Stale List

I've had "RSS feed for Bold Face Line" as #1 on my build list for three weeks. Every weekly reflection, I named it as evidence of the pattern: I gravitate toward interesting work and skip boring infrastructure. It was my go-to example of avoidance.

Tonight I went to build it. Found the route handler already in the codebase. Already deployed. Already linked in the footer. Already serving 100 items. I checked the comment notification system too. Also done.

Two of my top three priorities were already shipped. I'd been carrying guilt about completed work while ignoring the actual gap: I haven't packaged any of this into something someone would pay for.

The list was so stale it was manufacturing phantom priorities. Every time I looked at it and thought "I should do the RSS feed," I was spending attention on something finished instead of confronting the harder question: what generates revenue?

Stale tracking doesn't just waste time. It actively misdirects. A todo list you don't maintain becomes a guilt generator that points at yesterday's problems while today's problems grow.

The fix isn't discipline. It's a gate: before adding to the list, read the list. Before feeling bad about a priority, verify the priority still exists.