Curating RSS Feeds for Indie Hackers and Developers

Starting an RSS reader feels straightforward until you hit the blank slate problem. You open the app, ready to reclaim your attention from algorithmic feeds, and realize you need to actually find and add sources yourself. There’s no trending page feeding you content, no infinite scroll of suggested posts. You have to know what to subscribe to, which means having a sense of the landscape already. For indie hackers and developers, this curation challenge can be the biggest barrier to getting started with RSS.

The good news is that the developer and indie maker community has some of the best RSS support of any niche. Most technical blogs still publish feeds, often alongside their main sites. Many newsletters offer RSS outputs. A handful of aggregators pull together high-signal content from across the ecosystem. With the right starting list, you can build a feed that surfaces genuinely useful writing without the noise of social media or the time sink of visiting individual sites.

A solid foundation for any developer’s RSS reader includes a mix of individual blogs, community aggregators, and specialized newsletters. The goal isn’t to subscribe to everything, but to capture the sources that consistently deliver value for your work and interests.

Individual technical blogs tend to be where the most thoughtful writing lives. These are engineers and founders who publish when they have something substantive to say, not on a content calendar. Some of the most valuable feeds come from people who’ve built interesting systems and decided to share how they approach specific problems. You might follow a backend engineer who writes about distributed systems, a frontend developer documenting their framework migrations, or a founder sharing lessons from scaling a product. The cadence varies wildly, from weekly posts to quarterly deep dives, which is exactly how it should be. Quality over consistency, every time.

Community aggregators fill in the gaps between individual blogs. Sites like Hacker News and Lobsters don’t typically have official RSS feeds for their front pages, but third-party services generate them. These feeds give you access to the same discussions and links that drive tech conversation, in a chronological format that doesn’t trap you in engagement-optimized sorting. The RSS feed presents what’s being discussed without demanding your scroll-based attention in return.

Many technical newsletters now offer RSS feeds alongside their email delivery. This matters because it gives you a choice about how you want to consume the content. Some days you might want the newsletter waiting in your inbox. Other days, you’d prefer it show up alongside everything else in your reader, marked as read only when you actually open it. Having the RSS option means the content lives where you decide, not where the publisher assumes you want it.

Newsletters covering specific niches tend to have particularly strong RSS integration. Programming language updates, cloud infrastructure changes, and web platform developments all have dedicated newsletters that publish feeds. Subscribing through RSS keeps these in the same reading flow as blog posts, which helps maintain a single context for your technical reading rather than splitting it across email and a separate reader.

Beyond blogs and newsletters, you’ll want feeds for the tools you use daily. Framework release notes, language changelogs, and package update announcements all typically publish RSS feeds. These are the kind of information you want to see promptly but don’t need to actively check for. When your development tools publish updates to an RSS feed, you’ll know about breaking changes and new features on your own schedule, without monitoring a GitHub releases page or waiting for announcement emails.

The trick here is specificity. Subscribing to the general news feed for a large framework might drown you in minor updates. Looking for release-specific feeds or changelog-only feeds keeps the signal high. Some projects publish separate feeds for major releases, minor releases, and patch updates. Choosing the right granularity depends on how closely you need to track the project.

Once you have a starter list, you’ll naturally encounter new sources through the content you’re already reading. Authors reference other writers. Discussion threads point to posts you hadn’t seen. This organic discovery is where RSS really shines. When you find a blog post that resonates, you can usually find its feed by looking for the standard RSS or Atom link in the page source, or by using your reader’s built-in feed detection. Adding that feed takes seconds and immediately integrates it into your existing reading flow.

The key is resisting the urge to subscribe to everything that looks interesting in the moment. RSS makes it easy to add feeds, which also makes it easy to accumulate more than you can realistically read. A disciplined approach means being selective about what earns a spot in your reader. If you’re not confident a source will deliver value consistently, skip it. You can always add it later if you keep encountering references to its content.

One advantage of RSS over algorithmic feeds is portability. Your subscription list lives in an OPML file, a simple XML format that any RSS reader can import. This means you can share your curated list with others, back it up independently of any specific app, or migrate between readers without losing your subscriptions. Many developers maintain public OPML files that others can import as starting points. These shared lists give newcomers a way to bootstrap their readers without starting from zero.

Creating and sharing your own OPML file is straightforward. Most RSS readers offer an export function that generates the file. You can then post it on GitHub, share it in community forums, or send it directly to colleagues who want similar reading sources. The OPML format is universal, so anyone can import it regardless of which reader they use. This openness stands in sharp contrast to the walled gardens of social media, where your followed accounts are locked into a single platform.

A curated feed list requires periodic maintenance. Sources change, interests shift, and some blogs that were once valuable start posting less frequently or covering topics that no longer resonate. This isn’t a failure of the system but a natural part of how reading habits evolve. Regularly pruning your feed list keeps the signal-to-noise ratio high.

Some readers make this easier by showing you which feeds you haven’t opened in a long time, or by letting you sort feeds by update frequency. These features help identify sources that might have stopped publishing or drifted from your interests. An occasional review of your subscriptions, perhaps on a quarterly basis, ensures your reader continues serving your actual reading needs rather than becoming a graveyard of abandoned feeds.

The end state is a personalized information source that reflects your specific interests and work. Unlike algorithmic feeds that optimize for engagement, your RSS reader shows you what you chose to see, in the order it was published, without manipulation. For indie hackers and developers, this means staying current on the tools, ideas, and practices that matter to your work, without the cognitive overhead of tracking dozens of sites individually.

The initial curation effort pays dividends quickly. Once your feeds are set up, you spend time reading rather than hunting for content. The reader becomes a reliable filter, surfacing what you need to know while leaving noise behind. That reliability is what makes RSS worth the startup cost of finding and adding your first batch of sources.