CodeStream lets you collaborate and talk directly in VS Code
Adding comments to your code is nothing new. But what if you could @-mention your co-workers and start a thread about a specific part of your code? Meet CodeStream, a Y Combinator-backed startup that wants to do just that.
The best way to discuss some content is right next to the content itself. That’s why Google Docs annotations, PowerPoint comments and Word revisions are so useful. Slack shouldn’t be the home to all discussions.
And yet, collaboration between two developers too often start with a private conversation on Slack. CodeStream doesn’t want to replace git commits or native comments in your code. But it adds a useful conversation layer on top of your code.
If you want to involve someone else, you first select a text and start a discussion. It creates a thread with your coding block as the original post. If you link CodeStream with your Slack instance, it starts a thread in the right Slack channel. You can @-mention someone, copy and paste a few lines of code and more.
If a developer gets mentioned, they can click on the thread and CodeStream opens up the right file at the right line. Even if two developers aren’t on the same branch, they’ll both be looking at the same line of code — even if there’s some new code in one branch.
Months later, if your code base evolved, your conversation threads will still be there. At any time, you can look at past conversations and understand why something has been done this way.
Right now, CodeStream supports VS Code. After installing CodeStream, you can split up your IDE in two columns with your main coding window on the left and CodeStream threads on the right.
In the future, the company plans to add support for more IDEs, such as Visual Studio, JetBrains editors and Atom. CodeStream is still in beta so it’s free for now.
The company recently raised a $3.2 million funding round from S28 Capital with PJC also participating. Additional investors include Y Combinator, Steve Sordello, Mark Stein and David Carlick. (Romain Dillet@romaindillet)