Software engineer interested in systems, programming languages, and developer tools.

I like understanding how things work beneath the abstractions — and turning that understanding into small, useful software.

My current interests revolve around:

• Systems & Linux — Unix, operating systems, terminals, filesystems, networking
• Programming Languages — Rust, C++, and language/runtime fundamentals
• Developer Tools — CLI tools, automation, local-first software
• Learning & Knowledge — computer science, programming languages, and technical writing

Exploring Rust through both structured study and real projects.

• gg — a personal command-line knowledge base for Linux commands. Markdown notes, terminal/browser rendering, search, editing, and optional AI-assisted note generation.
• rustcamp — a structured Rust learning project covering language concepts, idioms, concurrency, async I/O, backend development, and more.

I'm particularly interested in the parts of Rust that force you to think carefully about ownership, concurrency, error handling, and system boundaries.

I spend a lot of time working in Linux and shaping my own development environment.

• nixos-config — my NixOS configuration and reproducible development environment.
• Shell, terminal tools, editors, system configuration, and Unix workflows are recurring subjects in my projects.

I maintain technical notes as part of learning rather than treating them as documentation written afterwards.

• cpp-modern-notes — notes on modern C++
• blog — technical writing and experiments
• rustcamp — structured Rust study

The goal is simple:

Learn something → understand it deeply → build something with it → write down what I learned.

I prefer understanding over memorizing, and building over merely reading.

I don't particularly care about using the most fashionable technology.

I'd rather understand why a system works, where its boundaries are, and what happens when things go wrong.