Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Your Software is Broken — Pay Attention by James Smith Your team has been tasked with releasing new and better versions of your product at record speed. But the risk of moving quickly is things break in production and users abandon your buggy app. To stay competitive, you can't just ship fast - you also have to solve for quality. We'll rethink what it means to actively monitor your application in production so your team can ship fast with confidence. With the right tooling, workflow, and organizational structures, you don't have to sacrifice release times or stability. When things break, you'll be able to fix errors before they impact your users. Help us caption & translate this video! http://amara.org/v/J37Y/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the talk "Your Software is Broken — Pay Attention," James Smith addresses the critical need for effective production monitoring in software applications. He emphasizes that while rapid deployment is essential to stay competitive, it should not come at the cost of software quality. Effective production monitoring allows teams to ship confidently by identifying and resolving issues before they lead to user dissatisfaction. Smith breaks down production monitoring into three core areas: stability monitoring, performance monitoring, and availability monitoring. Key points discussed include: - The importance of confidence in software reliability post-deployment: Developers must understand that simply shipping code is insufficient; ongoing monitoring is crucial. - Acknowledging customer frustrations: Common scenarios include users abandoning buggy apps that fail during critical transactions, like purchasing. A retention study highlighted that 84% of customers will cease using software after just two crashes. - Common pitfalls or 'deadly sins' of production monitoring include: - Assuming everything is fine post-deployment - Relying solely on customer complaints for insights - Lack of visibility into issues due to ineffective logging practices - Absence of accountability regarding issue ownership - Principles for improving production monitoring: - Accept that software can and will break; embrace this reality to foster a more proactive approach to issue resolution. - Use automated tools to detect problems promptly rather than relying solely on log files or alerts. - Prioritize alerts through effective aggregation and team communication tools to manage engineering efforts efficiently. - Accountability and ownership should be established within teams to ensure problems are addressed timely, promoting a healthy culture of learning from mistakes. In conclusion, James Smith urges teams to implement these best practices for effective production monitoring to enhance software quality and user experience. By recognizing the inevitability of issues, employing the right tools, prioritizing alerts, and fostering accountability, organizations can navigate the challenges of rapid software deployment while ensuring customer satisfaction and brand integrity.
Suggest modifications
Cancel
