Backend, security & infra
The plumbing: verifying tokens from several identity providers, reading data from sources that have no API, and keeping infrastructure boring with Terraform.
How I use Terraform on my projects: a boring AWS setup that holds up
Remote state, small modules, one directory per environment, plan on every PR, and the rules that keep Terraform on AWS from turning into a mess. With this blog's own infrastructure as the worked example.
One backend, five identity providers: a walkthrough of auth-reference
A tour of auth-reference, a small TypeScript API that verifies tokens from Firebase Auth, Amazon Cognito, Supabase Auth, Clerk and any OIDC provider behind one interface, built one provider per commit.
Reading bank notification emails to track spending in Colombia
Colombian banks don't offer open APIs to regular developers, so Nora reads the transaction alerts they already send by email. Here's how the pipeline works.
Other topics
- AI in production9LLM features that survive real users: contracts, evals, cost.
- Agents & automation3Agents, MCP servers and bots that do real work.
- Architecture6Frontend and backend structure that scales with the team.
- Backend, security & infra3Auth, data pipelines and the infrastructure under it all.
- Leadership & delivery2Leading small teams and shipping under constraints.