March 2018
Intermediate to advanced
244 pages
6h 10m
English
Over the course of this book, we’ve covered the broadly diverse landscape of adoption. Much of our discussion has focused on preventing our application from breaking in the first place. When your application does fail, and it will, you’ll need the right kind of data to diagnose the problem. Just as a good user interface designer anticipates the needs of a user, you the developer must anticipate your future needs when it’s time to provide support.
In this chapter, you will learn how to listen for failures and the tools available to debug your system when things go wrong. We’ll primarily worry about logging. We’ll find ways to keep your logs efficient and easy to read.
When we’ve considered those sources ...
Read now
Unlock full access