Developer drawn to the unglamorous half of software: the part that has to stay up at 3 a.m. I care about how systems behave under load, how they fail, and how to make failure boring. Working my way toward SRE and systems architecture.
Everyone says think outside the box. I've found the solution is usually inside the box. Reason from first principles, take the box apart, and see how it actually works.
What I'm doing right now
- 馃洜 Building Dot, a local-first shared memory layer for AI agents. SQLite + a vector index, a ranking engine, and a forgetting curve, all running as a quiet background daemon.
- 馃摉 Working through Designing Data-Intensive Applications (Kleppmann): replication, partitioning, consistency, and the tradeoffs nobody warns you about up front.
- 馃Л Going deep on distributed systems, observability, and the discipline of reliability.
What I reach for
Languages Python 路 TypeScript 路 C / C++
Systems Linux 路 Docker 路 Kubernetes 路 Terraform
Cloud AWS 路 Azure 路 GCP
Workflow Git 路 GitHub Actions 路 a healthy fear of untested deploys
A few things I believe
- Reason from first principles. Most "best practices" are just someone else's context.
- Boring, observable systems beat clever, opaque ones.
- The interesting question is never "does it work?". It's "how does it fail?".
- Write the decision down. Future-you is a stranger who doesn't return your calls.
The solution is usually inside the box.