TL;DR —
Write about a time when you struggled (and later, triumphed) to identify a bug or performance issue in your mobile application and the steps you took to ultimately solve the problem.
Some ideas to help you get started:
Do you remember those support tickets from customers writing in to report their application crashing or freezing?
Was it right after a new release?
Were you notified by a monitoring tool?
Did a problem arise from a 3rd party library?
Did a problem occur when receiving an unexpected HTTP response?
Testers, Debuggers, Software Developers, QA Specialists - here’s a treat for y’all: The #MobileDebugging Writing Contest by Sentry and HackerNoon. Here’s your chance to show your debugging skills to the internet and win $$$!
Share your #MobileDebugging Story!
Write about a time when you struggled (and later, triumphed) to identify a bug or performance issue in your mobile application and the steps you took to ultimately solve the problem.
Some ideas to help you get started:
- Do you remember those support tickets from customers writing in to report their application crashing or freezing?
- Was it right after a new release?
- Were you notified by a monitoring tool?
- Did a problem arise from a 3rd party library?
- Did a problem occur when receiving an unexpected HTTP response?
[story continues]
Written by
@hackernooncontests
Official account for all the writing contests powered by HackerNoon.
Topics and
tags
tags
mobiledebugging|debugging|sentry|hackernoon|performance|mobile-app-performance|software-development|programming
This story on HackerNoon has a decentralized backup on Sia.
Transaction ID: 9pi_KGgAjUQnu21RK_usrlVF2tU7NDa5ViZghkMu7ig