Application Crash Monitoring

With Software Engineering Daily
55 min
TABLE OF CONTENTS

    “The dirty secret of software is that you cannot fix every single bug.”

    Applications can and will crash — it is increasingly important for developers to have visibility into the reasons how and why the crash occurred. James Smith is the guest on the show today, and joins Jeff to discuss why modern applications crash, and how developer products are improving to tighten the gap between QA/support and dev. James is the founder of Bugsnag, an automated crash monitoring system.

    Questions

    • When an app crashes, how does a crash manifest on a user level?
    • What are types of application crashes developers need to worry about?
    • What language patterns are you noticing being implemented to deal with the common crash types?
    • What is automated crash detection?
    • How does the workflow of debugging and application development change after implementing an automated crash detection system?
    • What did the first version of Bugsnag look like?
    • What’s the future of Bugsnag?

    Application Crash Monitoring

    With Software Engineering Daily
    55 min

    “The dirty secret of software is that you cannot fix every single bug.”

    Applications can and will crash — it is increasingly important for developers to have visibility into the reasons how and why the crash occurred. James Smith is the guest on the show today, and joins Jeff to discuss why modern applications crash, and how developer products are improving to tighten the gap between QA/support and dev. James is the founder of Bugsnag, an automated crash monitoring system.

    Questions

    • When an app crashes, how does a crash manifest on a user level?
    • What are types of application crashes developers need to worry about?
    • What language patterns are you noticing being implemented to deal with the common crash types?
    • What is automated crash detection?
    • How does the workflow of debugging and application development change after implementing an automated crash detection system?
    • What did the first version of Bugsnag look like?
    • What’s the future of Bugsnag?

    Application Crash Monitoring

    With Software Engineering Daily

       /   
      PT
    55 min
    Decorative gold color tiles accent.

    What you'll learn

    “The dirty secret of software is that you cannot fix every single bug.”

    Applications can and will crash — it is increasingly important for developers to have visibility into the reasons how and why the crash occurred. James Smith is the guest on the show today, and joins Jeff to discuss why modern applications crash, and how developer products are improving to tighten the gap between QA/support and dev. James is the founder of Bugsnag, an automated crash monitoring system.

    Questions

    • When an app crashes, how does a crash manifest on a user level?
    • What are types of application crashes developers need to worry about?
    • What language patterns are you noticing being implemented to deal with the common crash types?
    • What is automated crash detection?
    • How does the workflow of debugging and application development change after implementing an automated crash detection system?
    • What did the first version of Bugsnag look like?
    • What’s the future of Bugsnag?
    Speaker(s)
    No items found.

    Application Crash Monitoring

    With Software Engineering Daily

    Application Crash Monitoring

    With Software Engineering Daily
    55 min

    “The dirty secret of software is that you cannot fix every single bug.”

    Applications can and will crash — it is increasingly important for developers to have visibility into the reasons how and why the crash occurred. James Smith is the guest on the show today, and joins Jeff to discuss why modern applications crash, and how developer products are improving to tighten the gap between QA/support and dev. James is the founder of Bugsnag, an automated crash monitoring system.

    Questions

    • When an app crashes, how does a crash manifest on a user level?
    • What are types of application crashes developers need to worry about?
    • What language patterns are you noticing being implemented to deal with the common crash types?
    • What is automated crash detection?
    • How does the workflow of debugging and application development change after implementing an automated crash detection system?
    • What did the first version of Bugsnag look like?
    • What’s the future of Bugsnag?

    Application Crash Monitoring

    With Software Engineering Daily

    55 min

    “The dirty secret of software is that you cannot fix every single bug.”

    Applications can and will crash — it is increasingly important for developers to have visibility into the reasons how and why the crash occurred. James Smith is the guest on the show today, and joins Jeff to discuss why modern applications crash, and how developer products are improving to tighten the gap between QA/support and dev. James is the founder of Bugsnag, an automated crash monitoring system.

    Questions

    • When an app crashes, how does a crash manifest on a user level?
    • What are types of application crashes developers need to worry about?
    • What language patterns are you noticing being implemented to deal with the common crash types?
    • What is automated crash detection?
    • How does the workflow of debugging and application development change after implementing an automated crash detection system?
    • What did the first version of Bugsnag look like?
    • What’s the future of Bugsnag?
    Speaker(s)
    No items found.