About
I'm a backend engineer working mostly in Go and PostgreSQL. Most of what I enjoy sits below the API surface: getting concurrency right, keeping schemas honest, and making failure modes boring.
I care about systems that are legible a year later. That usually means fewer abstractions than feel clever at the time, explicit boundaries between business logic and infrastructure, and letting the database enforce what the database is good at enforcing.
This site is also a log. Alongside essays, I keep track of what I'm reading, what I'm watching, and what I'm currently trying to learn.
Skills
Proficient
- Go
- Goroutines, channels, and interface design. Production services on Gin, pgx, and goose, structured with hexagonal architecture, Wire for dependency injection, and Squirrel for query composition.
- PostgreSQL
- Schema design, indexing, advisory locks, full-text search, and CHECK constraints as a correctness tool rather than an afterthought. Comfortable reading query plans.
- Python
- Scripting, automation, and data processing. FastAPI and SQLAlchemy for services, plus CLI tooling for internal work and quick prototypes.
- Git
- Branching strategies, interactive rebasing, and stashing. Comfortable with bisect for regression hunting, worktrees for parallel work, and untangling awkward merges.
Working knowledge
- AWS
- EC2, S3, RDS, IAM, and VPC. Deploying and operating infrastructure day to day through both the CLI and the console.
- Terraform
- Infrastructure as code across AWS resources: modular configurations, remote state, and plan-then-apply as a discipline rather than a formality.
Exploring
- Elixir
- Pattern matching, processes, and supervision trees. Working through Phoenix and OTP to understand fault tolerance from a different angle than Go's.