Backend engineer focused on building clean APIs and taming distributed systems. I spend most of my time in Go, occasionally venturing into Python or TypeScript when the situation calls for it.
- Go — primary language, day-to-day work
- Python — scripting, tooling, one-off automation
- TypeScript — when I have to touch a frontend or write a Node service
- Infrastructure / DevOps — Docker, Kubernetes, Terraform, the usual suspects
- Databases — PostgreSQL mostly, some Redis and etcd
Lately I've been building out some CLI tooling to make local Kubernetes development a bit less miserable. Also slowly working through improving observability patterns in a distributed tracing side project.
- APIs that are consistent and don't surprise you
- Services that fail gracefully and recover cleanly
- Docs that actually reflect how the thing works
- Email: lambert.dodd [at] proton.me
- Open to conversations about infra, backend architecture, or Go in general