Mr. Andrew Miklas co-founded PagerDuty, Inc. in 2009. He joined S28 in December 2017 and serves as a Partner. Mr. Miklas holds a BSE in software engineering from University of Waterloo from 2001-2006, and an MSc, in computer science from University of Toronto in 2006-2008.
Claudio Pinkus: Thanks for taking the time to talk to me today. The first question is what is it that you think makes for successful companies? What are the most important ingredients? Please narrow it down to the essence.
Andrew Miklas: I think the traditional answer – “founders, market, and product” – is pretty close to the right one. More specifically, my partners and I have a theory that for any successful startup, there are probably only seven or so unique factors that drive its success.
We’re excited to announce that CodeStream V0.11.0 for VS Code is now available. This beta release includes all of our latest functionality including:
Why discussions about your code must live with your code
The established process for software development in a team setting is a variation on this:
Get together in the beginning of the week and lay out the sprint.
Get your work done without becoming an annoyance to your team members.
Get together at the end of the week after you commit your code and hope it’s good enough.
The work gets done. Rinse. Repeat.
So we posit a hypothesis: Developers don’t ask enough questions and don’t communicate nearly enough about code. As a result, they don’t consult early enough with their team members and commit sub-optimal code.
We’ve received much feedback that having a separate chat stream for each source file didn’t mirror the way discussions were happening in the real world, where they often span source files. A discussion that starts with problematic code in one source file might end with relevant code being shared from another.
We’re going to be presenting a new version of CodeStream for Visual Studio Code, our #1 most requested editor, Monday through Wednesday next week at the Build Conference in Seattle. What’s cool is that Jonathan Carter, the lead PM on Visual Studio Live Share, will be demoing CodeStream’s integration with Live Share during one of the keynote presentations. We’re stoked.
If you are planning on attending the conference, or happen to be in Seattle, stop by booth E58 to check it out.
On Monday CodeStream was honored to present our company to over 2500 investors at YC’s twice-a-year Demo Day event. Thanks to our early supporters, we had a fantastic reception to our vision of dramatically improving the way software teams work together and build knowledge around their code.
More news to come but in the meantime checkout some stats from our W18 batch.
Two exciting updates from CodeStream, both of which will translate into fewer emails in your inbox. First up is our Slack integration. Once setup, all of your team’s messages on CodeStream will flow through to the channel of your choice on Slack. You can even reply to those messages right from Slack, and the replies will get posted to CodeStream. Definitely a good option for teams that have developers not currently using Atom.
We are proudly “Made in NYC” so we were thrilled to be featured at this month’s NY Tech Meetup event. Check out our Head of Product Dave Hersh’s interview as we continue to spread the word on the power of contextual messaging and integrated knowledge management for software teams.
Why You Should Do Something About Tech Debt
Every growing codebase in every industry is accumulating technical debt. The consequences of excessive technical debt are low productivity, high rate of errors, delays in delivering updates, higher costs, overburdened developers and less happy customers.
Since technical debt is inevitable, like death and taxes, the question is how to best manage its accumulation and reduction, and how to keep it at tolerable levels that will not result in bad business outcomes.
We started CodeStream because after years of working on news feeds and chat collaboration solutions, we realized that we were not applying what we knew about real-time collaboration to our own development processes. The team at CodeStream has been together for a couple of decades. We created a social network called Multiply, and a team chat solution called Glip. One day last year, as we were discussing code, it hit us that the available solutions, even our own previous efforts, were just not doing it for development teams. This post is about how to make team chat a lot better for hackers.