Code Like A Girl

Welcome to Code Like A Girl, a space that celebrates redefining society's perceptions of women in…

Follow publication

Member-only story

How A Simple, Stupid Error Keeps Crashing My App

Delfina 🌻
Code Like A Girl
Published in
8 min readFeb 11, 2025

Author Generated Image

Let’s start with the good news.

Not too shabby for a first timer!

Now, on to the bad news.

How is this even possible?

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Published in Code Like A Girl

Welcome to Code Like A Girl, a space that celebrates redefining society's perceptions of women in technology. Share your story with us!

Written by Delfina 🌻

Learning iOS development by doing. Currently building my pasta-themed Pomodoro app, FocusPasta!

Responses (9)

Write a response

These are the kind of situations when tests could come in really handy. Refactors are high-risk, and a pretty bullet-proof way to mitigate those risks is have tests. It doesn't even have to be unit tests, even some E2E tests for all the possible UX flows would catch this one quite easily.

--

Amazing write up! Have you looked into tools like Sentry? It'll record steps taken by the user before the error which can make it easier to figure out the combination that causes issues, plus it'll log it to a nice UI and give you a bunch of stats that can help triage bugs

--

Love a good detective story!

--