1. 1
   
   Tech Note2026.05.08

   80 defect reports in GS certification taught me what a defect actually is (Part 1)

   Three weeks of GS certification testing produced 80 defects, but fewer than half were code bugs. The rest were behaviours a user could not confirm.

2. 2
   
   Tech Note2026.05.20

   Replacing password hashing with argon2id on a live system (Part 2)

   A GS certification security defect meant replacing unsalted SHA-256 password storage with argon2id — on a live system, without interrupting login.

3. 3
   
   Tech Note2026.05.30

   Rebuilding error handling so failure says it failed (Part 3)

   GS certification flagged a success message and an error log on one screen. Rebuilding error handling: field validation, specific text, no silent failures.

4. 4
   
   Tech Note2026.06.09

   If changing the setting changes nothing, that is a defect (Part 4)

   Most of the 36 defects in the third GS certification report were node options. Repairing the broken ones and making the invisible ones observable.

5. 5
   
   Tech Note2026.06.16

   The manual was part of the product: what three weeks of GS certification left behind (Part 5)

   Much of the 30 usability defects in GS certification were documentation, not code. Moving the PDF manual to an MkDocs wiki, and fixing Korean IME input.