#debugging
4 posts- 3 min
"OK" doesn't mean it opened — chasing a PDF that never appeared
Open a Mac file from the iPhone. Run it, and the log says "ok." But on the Mac's screen, nothing happens. The hunt for the culprit ended somewhere unexpected — an app that had been left running for fourteen days. And the real lesson wasn't about the culprit. It was about the "ok."
- 2 min
Every real bug becomes a test — one receipt stands guard
A discount line vanishes entirely. A payment made with iD gets recorded as cash. With something as endlessly varied as receipts, fixing one may be breaking another. So I decided to turn every receipt that tripped me up on a real device into a test, on the spot. The story of how the receipt that troubled me becomes a guard.
- 3 min
It froze on the fifth — when debugging changes the spec
The machinery was in place. But scanning several cards in a row, the screen froze around the fifth. Offloading the heavy work, trimming the memory — both were correct improvements. Yet the real way out lay further on. Chasing the bug, I'd ended up rebuilding the way the app captures, without noticing.
- 2 min
I stopped saying "the focus seems soft" — facing a placeholder number
A perfectly readable card sometimes got dropped with "the focus seems soft." Tracing the cause led to a gate placed before text recognition, and a single number left standing there. "Provisional — tune on device": a number marked that way, and then never touched again.