Subscribe
Sign in
CodeStream — Discuss, review, and understand code from inside your IDE
CodeStream's cloud-based service and IDE plugins help dev teams discuss, review, and understand code. Enhance your existing services by connecting them to your source tree, and capture knowledge about your codebase while streamlining existing workflows.
47
Replies
Peter Nixey
This is such a lovely idea and kudos to you guys for executing on it so well. I haven't had the chance to use it yet but I've read the comments and seen some of the YC backchanneling and you've obviously hit this in the right place. I'm really excited for you guys and to see where this goes!
Share
Five years from now developers will be thinking in terms of two eras: BC (Before CodeStream) and AC (After CodeStream).
Pros:Cut and paste code to Slack was cool. This is next level. Topic #1 from our last launch was collaborating through the DLC. =SOLVED
Cons:Too early to tell. 30 seconds to add from VS extensions. Side effects may include denial and depression from loss of life before CodeStream.
I love this, @peter_pezaris. What's on your product roadmap over the next few months?
@tomhadfield Two big projects currently underway are MS Teams support and a Docker-based on-prem solution. Then Eclipse and Sublime support. Plus a few surprises we're keeping close to our vest for now :)
Our team has been using the IntelliJ beta for a few weeks, and... how did this kind of tool never exist until now?
We used to copy-pasta code back & forth between Slack & our IDE just to ask each other questions, and it seriously feels like we just woke up out of the dark ages with this tool. Like, this is just how things should work. Period.
Oh, and bookmarks are amazing. Thought they'd be useless (I can temporarily comment my own code, right?), but turns out to be a total game-changer when I need to grok new codebases.
@haoyangnz Thank you very much! Let me know if you have any feedback once you've had a chance to try it out.
This is a really cool new approach to documentation. As opposed to comments (which tend to quickly get outdated) or dry and lifeless API docs, CodeStream lets you peek behind the curtains and understand the thought processes and discussions that underly tricky sections of code through multiple iterations.
These discussions are currently taking place in Slack or other tools, but because they lack any connection to the code, they aren’t easily discoverable to a developer. CodeStream fixes this by integrating at the IDE level, making all that meta-knowledge that used to disappear into the ether feel like a direct extension of the codebase.
The ever-growing list of integrations is awesome.
Pros:Feels like the future of developer collaboration. Very well built product; never encountered any bugs.
Cons:Requires a bit of wrangling to get your team to buy in and adopt it, just like any workflow tool. Well worth it though!
@davidoudiette Thanks David! Please be sure to send us feedback once you've had a chance to check it out.
Solid product! But why does Codestream need the following Slack access : "CodeStream will be able to read all messages, files and profiles that you can access"? @peter_pezaris
@zaccooner CodeStream’s Slack integration allows you to share codemarks to any of your Slack channels or DMs. You and your teammates can participate in the conversation from either CodeStream or Slack, with messages in Slack being posted as the real users (as opposed to CodeStream bot). CodeStream is effectively acting as a Slack client, with messaging going directly from the IDE client to Slack’s backend (i.e., not going through our servers).
This model provides a great user experience, but unfortunately, in order to do this Slack requires us to ask for those seemingly scary scopes. We’re exploring other options here, but hopefully the face that your Slack messaging isn’t going through CodeStream’s servers will give you peace of mind.
@zaccooner @dhersh Put another way, you're not granting CodeStream those permissions, since your Slack data does not flow through CodeStream's servers, but rather you're granting *yourself* those permissions, so your IDE can effectively become a slack client.
Hi everyone!
Understanding code that you didn’t write can be hard. We built CodeStream to make it easier to ask questions and get answers about how specific code works, and save those interactions where they below: with the code for the benefit of everyone one the team -- whether it’s next week, next month, or next year.
If you’ve ever looked at some code and had the question “what is going on here?” you'll appreciate what we're trying to do. So please download CodeStream, try it out, and let me know what you think!
As an executive level manager I don't deal with "code" directly but I can see how CodeStream will be a valuable tool in increasing efficiencies and collaboration among developer teams.
Pros:Excellent interface and easy to understand/follow.
Cons:Couldn't find any.
I've got to admit, whenever i'm looking at a chunk of code and need to ask clarifying question, my workflow was to find the file in Github, then find the line, click on it, go back to Slack and then message the person I wanted to ask the question. Usually by this time, I forget what i was about to ask :)
This product addresses one of the biggest problem i've faced working for a large organisation. Slack has become a massive pain to deal with with so much non-important but interesting stuff to distract you from getting shit done. I can still be on my editor and talk about code, and not deal with the slack social banter? Sign me up!
PS: I can't use this at work, but i'm going to give it a shot on my slack workspace/GitHub project. Thanks for making it and good luck!
@kunday thanks for the thoughtful reply. This is exactly one of the use-cases we hope to simplify with CodeStream, although our larger mission is to SAVE that information in a way that can benefit the next developer on your team who might have the same question.
CodeStream tags blocks of your code with the ID of the slack conversation thread, so that when any developer opens that file, our plugin can show you the discussion about that code. We implemented a "comment drift" algorithm to place that comment in the right place in your file, so if you commented on line 100 in one version of the file (let's say where a function started) but then in a future commit added 10 lines of new code above that, then CodeStream keeps your comment in sync with line 110. This way we can turn your conversation into documentation.
@spencer_cassidy thanks very much! please let me know whatever feedback you may have once you give it a shot
Ditto on many of the comments I've seen on this site and others about CodeStream: once you use it, you're baffled how it didn't exist previously. It's that fundamentally useful.
@howard_howard Thanks for the comment. We actually get that reaction a lot, especially after doing a demo. To be honest when we first thought of the product we were sure someone had done it before, but it turns out nobody had. I guess somebody had to be first?
the square root of 121 is 11. 999 of 1,000 adults do not know this simple fact. Marcus Aurelius was born 121 AD. He taught simplicity, “Ask yourself at every moment, ‘Is this necessary?’” Code Stream is
Pros:intuitive interface. Why wasn’t something like this available before now?
Cons:it has a terrible singing voice
@glenn_dorsam not yet; VIM will be difficult to support but we're hoping for something in a few months.