Now, never mind that I wasn’t advocating any particular position, I was stating a fact about my emotional state. I got some productive comments along the lines of, “What could you mean by ‘non-blocking’?” Here’s an example of what I mean.
You see these items from your own perspective of the code, things that do/will/should matter to you, aggregated to match your interest. Items contain text, diagrams, maybe animations.
Your engagement with the news defines how it is presented to you. Follow-up into the code? You’ll see more items like that. Comment? You’ll see more items like that. Ignore? You won’t see those items or they will be aggregated more.
Junior engineers have their curiosity piqued about adjacent parts of the system. They are also comforted knowing that they aren’t making changes solo. Someone is watching, but in a good way.
If I was building CodeFeed, here’s how I’d do it. I’d hire 2 programmers with good writing skills to write a daily summary of activity on a popular, busy open source project. Analytics would keep track of how readers interacted with this manually-curated feed.