Uses

The machines I type on every day.

• Lenovo IdeaPad Gaming 3

  My personal workhorse — handles coding, gaming, and homelab experiments alike.

• HP ProBook 450 G10

  The work laptop for day-to-day engineering tasks.

• Skyworth Monitor

  An external display for extra screen real estate at the desk.

• Press Play Keyboard

  A mechanical keyboard that makes the typing feel just right.

Apps I keep open all day.

• Arch Linux

  My main operating system — minimal, bleeding-edge, and bent exactly to my workflow.

• Windows

  Kept around for the times a tool or game only speaks Windows.

• Vivaldi

  My primary browser — endlessly customizable with tab stacks and panels.

• LibreWolf

  A privacy-hardened Firefox fork for browsing that minds its own business.

• Obsidian

  My second brain — Markdown notes linked together in one local vault.

Where the actual building happens.

• VS Code

  My go-to editor when I want a full-featured IDE experience.

• Neovim

  Terminal-first editing for when I want to stay on the keyboard and move fast.

• WezTerm

  A fast, GPU-accelerated terminal that I configure entirely in Lua.

• Languages

  Python, Go, Rust, and TypeScript — the languages I reach for most.

• Containers

  Docker and Podman for reproducible, isolated local environments.

• Version Control

  Git, always — with a soft spot for a clean commit history.

My personal playground for breaking and learning things.

• Servers

  Ubuntu Server and RHEL running my VMs and self-hosted services.

• Orchestration

  Terraform to provision and keep the lab declarative and repeatable.

• Monitoring

  Grafana for dashboards, backed by VictoriaMetrics for time-series storage.

The tools I reach for when shipping to production.

• Cloud Providers

  GCP, AWS, and Tencent Cloud, depending on what the project needs.

• Infrastructure as Code

  Terraform for provisioning and Ansible for configuration management.

• CI/CD

  GitHub Actions, GitLab CI, and Jenkins to automate builds and deploys.