Lazy-loading is the most ironic term in programming. That’s because, instead of eating its third bowl of cereal on the couch, what lazy-loading actually does is make your User Interface more efficient. And efficient UI is important to us at Sentry. We don’t want our customers tapping their feet and pointing to their imaginary watch while waiting for their page to load.
As the adoption of GraphQL is rising steadily, teams often come across the natural question of how to deal with errors that pass service boundaries and propagate from API endpoints to clients and consumers.
iPod to iPhone. Breaking Bad to Better Call Saul. Super Mario to Mario Maker. Leaders don’t rest on their laurels. That’s what motivated us to create Performance, our new code monitoring offering: to build off our core functionality and toward the demands developers face, both today and in the future.
Crashes are something we know a thing or two about. We see a lot of reasons why apps crash, but we also see when a lot of popular mobile apps crash at once, that’s something we notice. Crashes across many mobile apps at the same time is not typically a result of an app-specific code update. I mean, there’s a non zero chance that hundreds of developers published broken apps… but these widespread issues are likely a result of two things.
