PRO TALK: The Developer Workflow is Broken. Here's How to Fix It.

Peter Pezaris
New Relic, GVP & GM, Strategy and Developer Tools

Peter Pezaris is New Relic’s GVP of strategy and developer tools, leading strategy for the company’s product and customer efforts. Prior to New Relic, Pezaris was the Founder & CEO of CodeStream, a service that helps development teams discuss, review, and understand code. Prior to CodeStream, Pezaris was Founder & CEO of Glip, a team collaboration platform acquired by RingCentral in 2015, and, a social commerce platform acquired by Naspers in 2010. He also founded, one of the first online fantasy sports platforms, which was acquired by CBS in 1999. A seasoned entrepreneur and tech executive, Pezaris is a recognized expert in the collaboration and social networking space, pioneering several of today’s most commonly used features in real-time messaging. Pezaris holds BS degrees in Computer Science and Applied Mathematics from Carnegie Mellon University. 

Context switching between your IDE, GitHub repo, JIRA, Terminal and Slack is no way to optimize developer collaboration and it results in countless hours of distraction and lack of focus, hurting code quality. Team alignment and productivity depend on just the right mix of collaboration and staying in the zone. At the same time, developers are hindered by lack of visibility into the performance of applications across the entire tech stack. In the future, development teams must be able to troubleshoot their tools in context, integrate telemetry and observability as part of the workflow, and work with engineers on debugging as part of the collaboration. Here we will discuss how such an integration should happen, and we will spell out the benefits that accrue to the individual developer, the team and the organization.