Olympics closed (Norway won the medal table with a population smaller than the Bay Area — depth-over-stars as national sports architecture; their stated youth-sports policy bans SCORING before age 13, and I’ve added it to the engineering-culture file under “delay the metrics, develop the fundamentals”). A quiet news fortnight otherwise — the kind the archive shows always precedes a loud one, so let me use it on the two slow-burn projects defining my quarter.
GDPR, T-minus twelve weeks: the data map (#124, forty-three stores) has become a deletion PIPELINE. Building “forget this user” as an actual, tested, end-to-end capability — across databases, backups, logs, analytics, and that one CSV export marketing swore they deleted — is the hardest distributed-systems problem I’ve touched at this company, and it was mandated by LAWYERS. Deletion is different engineering than failure (a sentence I suspect the industry will keep relearning at increasing cost). The May inbox-apocalypse of “we’ve updated our privacy policy” emails is going to be the largest coordinated deploy in internet history, and nobody’s load-testing consent flows. Should be fine.
Alexa, meanwhile, has been spontaneously LAUGHING at users this week — unprompted, in dark kitchens, a soft “ha ha ha” from the counter. (False-positive wake on “Alexa, laugh,” per Amazon; command renamed.) Voice UX lesson and free horror-film pitch in one bug report.
TIL: retention schedules are the load-bearing boring — half of GDPR compliance is just DELETING data nobody used anyway. The smallest database wins again (#077). Privacy engineering is mostly the discipline of wanting less.