Week 019 — Routing Exposes an Architecture Problem
"Building the found item flow requires URL routing for QR codes, which immediately surfaces a deeper problem: the hybrid page-loading model breaks session validation."
"Building the found item flow requires URL routing for QR codes, which immediately surfaces a deeper problem: the hybrid page-loading model breaks session validation."
The DTO/Service/Repository refactor meets reality. An entire new class structure, built without testing, reveals its bugs one by one.
"Building DTO classes for the item refactor raises a design question with no clean answer: how do you handle an object with a lot of optional fields?"
A month away from the project. Coming back, the found item logic resumes, Grok introduces the DTO pattern, and a refactor begins taking shape before the feature is even finished.
"The lost item feature lands — save, reward, visual state — and immediately surfaces a design question: found and safe are not the same thing."