It’s Time for a Technical Newsfeed

A few months ago we began experimenting lightly with a newsfeed and I even built a prototype based on what we believed would be most useful for a software professional.

Although we’re one-hundred percent committed to building out our analytics platform we know that the communication of that data is just as fundamental of an ingredient so that we can move toward actionable insights.

A newsfeed, of some sort, feels about right.

So we’ve continued to experiment and prototype out a few different versions, getting closer to something that feels relevant, contextually powerful, and of course, useful to an end-user.

Here are a couple of gifs that capture some of the very first iterations that are leveraging our existing datasets and models. Take a look:


The first one here is what you might expect – a simple notification system that alerts you about events that you’ll want to know about in your #EngOps universe which might be related to a critical notification from your continuous integration tooling or quality assurance suite.

Or, it could be a message around a ticket that you’ve been working on or something community-driven, like feedback on the upcoming corporate standup. As you know there are 1,000 different things that happen during your day so bubbling up the right things is what we’ll aim at doing next as we continue to experiment.

And, naturally, a notification system needs a formal place for see all of what is happening which leads us to a Technical Newsfeed or Engineering Operations Newsfeed (#EON…?):

Technical Newsfeed

Of course, there’s no styling right now but you get the gist and, from what we’ve seen and experienced already we couldn’t be more excited.

In fact, we believe that it’s high-time for a developer-centric newsfeed to be brought to market. We believe that it’s about time for the confluence of a developer’s universe and the many other disparate operational functions that they are required to engage with come into a single canonical source.

And, we believe that it doesn’t have to be altogether different to be incredibly useful. The user behavior that already exists around social (e.g. Facebook, Twitter, etc.) and technical (e.g. GitHub, Jira, etc.) doesn’t have to be rewired or recreated (i.e. build it right the first time).

At the end of the day our mission still hasn’t changed: We’re committed to helping individuals, teams, and organizations build better software and to start we have to give our developers and teams better tools.