W51 - Sharing and Summarizing High-Quality Information Sources
Over the past two years I have been gradually collecting primary sources; recently I reorganized the 77 RSS feeds in my Feedly. I’m sharing the OPML file at the end of the post — feel free to download and import it.
I categorized the sources by primary role to make it easier to choose different reading scopes based on available time and focus. They’re divided into three groups: Individuals, Industry & Organizations, and News & Communities.
Indie Blogs: Pursuing perspective and depth
This category mainly covers personal blogs by independent developers, technical experts, and industry observers. Their articles often carry a strong personal voice and distinctive analytical frameworks.
AI signposts: such as former OpenAI researcher Lilian Weng and Sebastian Raschka; high-quality podcasts like Dwarkesh Patel and the Lex Fridman Podcast;
Traditional yet open programmers: such as Martin Fowler (author of Refactoring) and Simon Willison (Django); personal media that became brands, like The Pragmatic Engineer (top Substack programming channel) and KK’s The Technium;
Tech humanities and perspective: topics vary widely but can yield unexpected insights. Examples include Ruan Yifeng’s blog, Stratechery by Ben Thompson, and Bloomberry;
Industry & Orgs: Acquiring facts and industry practices
This category aggregates engineering blogs from major tech companies, official release channels, and academic preprints. It captures representative industrial best practices and cutting-edge academic breakthroughs. Venture capital and industry consulting firms are also included.
AI signposts: such as Anthropic Research, the OpenAI Blog, and Google DeepMind News; paper updates from arXiv (cs.AI) and Hugging Face Daily Papers;
Language and ecosystem official channels: such as the Rust Blog and the TypeScript official blog; standards and public goods like Recent RFCs, Google’s Chrome, and web.dev;
Engineering platforms and consultancies: major engineering platform official blogs like GitHub, Microsoft for Developers, Hugging Face, LangChain; venture and industry consultancies such as a16z, YC, Thoughtworks, MIT Sloan, Gartner, McKinsey;
News & Hubs: Maintaining breadth and instinct
This category includes aggregator media, community hot lists, and reporting from professional journalists. It primarily provides breadth and immediacy, enabling quick scans of industry hotspots and a sense of market sentiment.
Communities with high geek concentration: such as Hacker News — HN keeps only the minimal necessary publishing functions. There’s a great site, zeli.app, which provides real-time summaries for faster HN browsing; it’s clean and ad-free and highly recommended. Product Hunt collects the world’s latest product ideas and its lists are very valuable. Also vertical channels on Medium and Reddit, like LeadDev, Level Up Coding, and r/artificial;
Mainstream tech media: standardized industry reporting such as TechCrunch, The Verge, The Information, MIT News; in-depth interviews, for example Wired’s Gear column — KK once had a profound influence on the Gear column and the technical aesthetic and futurist orientation it represents;
Internet information distribution has gone through four phases — portals, search, subscriptions, and recommendations — with increasing distribution efficiency, but quality still requires continuous, intensive personal iteration. The approach I’ve found works best for me is combining Twitter’s algorithmic recommendations with Feedly’s subscription management. Together they cover almost all the sources I want to follow and help me avoid missing too much on timeliness and trend tracking.
Things to continue in 2026:
With information exploding, I still use brute force to carve out more time each day to browse, manage, and process content. To cope with the flood of information: first, exercise restraint — as taste improves you must continually prune and replace; second, build a more engineering-driven personal recommendation tool.
I’ve mostly finished assembling open sources and now want more ways to uncover semi-closed or closed high-quality sources. Not everyone publishes RSS or uses Twitter. Some publish on other platforms like LinkedIn or newsletters; some require paid subscriptions. Others don’t habitually publish publicly and only communicate in closed or semi-closed environments — after all, public expression requires an investment of attention.
Adopt and adapt these practices into new team workflows. Last year, the team’s AI coding study sessions were mediocre — everyone’s attention is limited, and I found many people don’t know what to read or where to invest their scarce attention. This is an area I want to influence over the long term.
Attachment: As of 2025-12-23, the 77 RSS feeds in Feedly.
Last updated