How do you Know it Works?

You get assigned a Jira ticket. Send users to a new checkout sub flow when they open the app through a new deep link.

Simple enough, you think. Find your navigation configuration. Write a few lines of code to wire up the deep link. Use code generation templates or an LLM to write the new screen and its components. Spin up your simulator, hit the deep link, see the new flow.

You make a new PR. Link to the Jira ticket. Write a short description. GitHub assigns a reviewer. You move on to the next ticket.

Wait. Tragedy. Changes requested?

The reviewer couldn't get the flow to trigger. Turns out you had a false positive because local state you modified during development stuck around. You have to figure out their bug report, ship a fix, go through review again.

Here's how you can avoid this common and frustrating scenario. When you're submitting a PR, slow down and ask yourself "how do I know it works?". Talk it through. Write it down. Then actually try your own verification steps. It's not as fun as typing on the keyboard or watching the unit tests go green. But you can save everyone some time by taking a little extra care when you submit your work.