The notebook
Thoughts, built on
experience.
Implementation details, tradeoffs, and the reasoning behind the code.
5 articlesSubscribe via RSS ↗
Building a Private Family Photo Vault Without Overengineering It
How I designed a private photo synchronization system by adding complexity only when a requirement justified it.
In the series · Private Family Photo VaultKeeping a Family Archive Small Enough to Operate
How storage cost, deletion semantics, mobile limits, and observability shape a private archive without requiring a larger platform.
In the series · Private Family Photo VaultA Gallery Should Not Download Your Archive
Why photo previews became a separate asynchronous workflow, and why a correct cloud object is only one part of a working mobile gallery.
In the series · Private Family Photo VaultResuming Uploads Without Starting Over
How the mobile client and S3 reconcile multipart sessions, refresh upload permissions, and recover when completion or cleanup changes remote state.
In the series · Private Family Photo VaultSynchronization Is a Reconciliation Problem
Persistent local state, account-scoped idempotency, and an Android failure that showed why bounded workers must make durable progress.
In the series · Private Family Photo Vault