Lyft’s Tips for Avoiding (Software) Crashes

2 years ago thenewstack.io

Summary: This is a summary of an article originally published by The New Stack. Read the full original article here →

Understanding what caused an app to crash is quite an undertaking. Bugs can happen anywhere in the codebase and vary in complexity and actionability (the engineering effort required for the first improvement).

Here’s what was found: Native crashes were not included in Lyft’s internal crash rate tracking.

They reported the crashes to Google Maps (cause of the crashes) and both teams are working together to resolve.

Lyft engineers weren’t expecting such a large impact on native crashes but apparently, the cause of many native crashes was low application memory.

DevOps Articles