Week 021 — Geolocation, HTTPS, and a Relative Path
Building the found item API backend, adding geolocation capture, getting HTTPS running in the dev environment, and a relative path bug hiding in plain sight.
Building the found item API backend, adding geolocation capture, getting HTTPS running in the dev environment, and a relative path bug hiding in plain sight.
Building the found item experience — returning options, QR code routing, user data refactored to support it — and a week of cascading design decisions.
"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?"