Rules to Better Error Handling

We're all aware how painful it can be when you see a nasty error message. In the best case it makes you feel uneasy and at worst it leaves you blocked.

The user experience should not be an incredibly jarring jumble of text that looks like it is designed for a computer 🤢. On the other hand, a developer should not be developing new features when they are oblivious to the unhealthy state of the application.

For developers, it is crucial to log errors, watch them daily and review the health of the application in the Sprint Review.

Let's jump in and look at some of the best practices.

youtube: https://www.youtube.com/embed/Zr4styC6S-E