I enjoy peeling away abstraction layers.
Every project I build begins with the same question:
How does this actually work?
That curiosity has taken me from web development into Linux, networking, infrastructure, distributed systems, developer tooling, and Rust. I am working toward understanding computers across the stack—not only using the tools, but learning why they exist and how they are built.
Learn deeply. Build from first principles. Share what you discover.
- 🦀 Rust and systems programming
- 🐧 Linux, Linux internals, and operating-system concepts
- 🌐 Computer networking and high-performance APIs
- ☸ Kubernetes, cloud infrastructure, and platform engineering
- 🏗️ Distributed systems, data modeling, and observability
- 🔧 Developer tooling, automation, and self-hosting
Reading gives me the vocabulary; implementing gives me the understanding. I use small, focused projects to explore the layers beneath the software I use every day:
- An HTTP server from scratch
- A Git implementation from scratch
- A Grep implementation in Rust
- A tmux configuration parser in Rust
- A production-oriented Express template
- Linux dotfiles and ESP32 hardware experiments
Every repository is an experiment—and a record of one more layer understood.
| Project | What I explored |
|---|---|
| http-server-javascript | How an HTTP server works from the socket up |
| codecrafters-git-javascript | Git's objects, references, and plumbing |
| codecrafters-grep-rust | Building a command-line search tool in Rust |
| toy_tmux | Parsing tmux configuration in Rust |
| template-express-base | A maintainable, production-ready Express starting point |
| dotfiles | A Linux setup managed with GNU Stow |
| arduino-esp32-projects | Hardware and embedded-systems experiments |
I keep my learning visible through projects, experiments, and notes. The thread that connects them is simple: understand the abstraction, then build a small version of it.
Current rabbit holes include Linux From Scratch, Arch Linux, NixOS and Home Manager, i3, Neovim, shell scripting, networking, containers, and Kubernetes.
I've contributed to projects including ws, mongoose, and Zed. I am especially interested in contributing to developer tooling, infrastructure, and systems software.
Hardware
↓
Operating systems
↓
Linux & networking
↓
Infrastructure & containers
↓
Kubernetes & distributed systems
↓
Reliable backend engineering
I believe understanding these layers helps us build software that is simpler, faster, more observable, and more reliable. Long term, I want to build infrastructure and backend systems—and eventually a consultancy—around that standard.
I don't want to know only how to use technology. I want to understand why it works.