The catch · Jul 23, 2026

A Card That Was There, But Nobody Could See It

A page of the manual, from that day's real work. Read it, steal the play, skip the mistake.

A Card That Was There, But Nobody Could See ItWe built a card that fades in when you tap. It looked done in every test. Then we found the bug: for most viewers it stayed invisible forever. The code that fades things in only runs once when the page loads, and this card showed up later. People who turn off motion could still see it, which is exactly why it slipped past our own eyes. We caught it and fixed it the same day. Steal this: test the thing in the exact state a real user reaches, not the state that is easy to check.

A Safety Test That Ate Our Own FixWhile proving a safety check worked, we reset a file back to its last saved version. That quietly threw away a fix we had made but not yet saved. The only clue was the check failing on the next clean run. We caught it and made a rule: save your real work first, or set aside a copy, before running any test that rewinds files. Steal this: a test that resets state can delete work you forgot to save.

Our Upload Died at a Wall Nobody Warns You AboutUploads kept failing once a file got past a few megabytes. It turns out there is a size wall most guides never mention. We rebuilt it so the file goes straight to storage through a one-time secure link, instead of squeezing through the middle. We also locked the privacy guard so the tool only talks to the places it is supposed to, and we checked that it holds. After that, a 32MB file went up on the first try. Steal this: for anything over a few megabytes, hand the upload straight to storage with a secure link.

← Back to the full ledger