Every error does not concern every engineer. Your team members don’t need to be pinged about every application error, especially when an error occurs in someone else’s part of the code. In fact, it can become a negative distraction that takes away focus from their work.
Creating a Culture of Code Ownership
DeveloperWeek 2021
*If the form isn’t loading or submitting properly, please 1) disable ad blockers, 2) enable cookies, and 3) turn off any tracking protection features. Still can’t see the form? Reach out to events@bugsnag.com.
What you'll learn
Every error does not concern every engineer. Your team members don’t need to be pinged about every application error, especially when an error occurs in someone else’s part of the code. In fact, it can become a negative distraction that takes away focus from their work.
Every error does not concern every engineer. Your team members don’t need to be pinged about every application error, especially when an error occurs in someone else’s part of the code. In fact, it can become a negative distraction that takes away focus from their work.
Every error does not concern every engineer. Your team members don’t need to be pinged about every application error, especially when an error occurs in someone else’s part of the code. In fact, it can become a negative distraction that takes away focus from their work.
Fill out the form on this page to gain access to the free on-demand talk.
Every error does not concern every engineer. Your team members don’t need to be pinged about every application error, especially when an error occurs in someone else’s part of the code. In fact, it can become a negative distraction that takes away focus from their work.
*If the form isn’t loading or submitting properly, please 1) disable ad blockers, 2) enable cookies, and 3) turn off any tracking protection features. Still can’t see the form? Reach out to sales@bugsnag.com.
