Currently focused on privacy by design at the application layer;
will expand with the other foundational topics — observability,
secrets handling, error handling, configuration — as they earn
their own pieces. Less prescriptive than the
guides, more focused on the questions to ask before
writing the code.
After this series: early-career developers approach every new
feature with the privacy-by-design habits — log what’s needed not
who did it, return only the fields the caller asked for, minimise
schemas by default — that shape what the code looks like from day
one.
Who this is for: developers in their first year or two of writing production code, and the engineers and team leads mentoring them. If you operate the infrastructure rather than write the application, the companion piece is privacy-by-design-server-build.
Introduction Most developers learn privacy backwards. They ship a feature; later someone in legal or security flags an issue; later still they retrofit the fix. By that point the data model has been baked in, the API contract is in production, and the rollback is more expensive than the right-thing-to-do would have been on day one.
...