Skip to content
~/uses
~/uses

What I build with

The real setup behind the site. Home is the terminal, Arch-flavored, riced, keyboard-driven, and everything below earns its place daily.

Environment

sys/env
Arch Linux
Yes, btw. Rolling release, minimal, mine to break and fix.
Hyprland
Tiling Wayland compositor, keyboard-driven, riced, fast.
Neovim
Configured in Lua. The editor I actually think in.
zsh
With a terminal open for basically everything.
tmux
Persistent sessions so nothing is ever really closed.

Languages & runtimes

sys/lang
Python
ML, data, scripting, and most of my project code.
TypeScript / Node
Full-stack web, APIs, this site.
C++
When performance and the metal matter.
Bash / Lua
Glue, automation, and config.
SQL
PostgreSQL and SQLite for the data layer.

Tooling

sys/tools
Git + GitHub
Version control, CI with Actions, and where the work lives.
Docker
Reproducible environments; ship it the way it runs.
PyTorch / TensorFlow
Training, fine-tuning, and evaluating models.
Apache Spark
When the dataset stops fitting in memory.
Power BI / Pandas
Turning messy data into dashboards people trust.

How this site is built

sys/web
Next.js + TypeScript
App Router, RSC, static generation.
Tailwind CSS
OKLCH design tokens, dark-first with a real light mode.
Motion + three.js
Purposeful animation and the interactive 3D core.
Vercel
Deploys, analytics, and speed insights.

Hardware

sys/hw
Linux laptop
The daily driver, light, fast, and fully in my control.
Mechanical keyboard
Because the terminal is home.
A second monitor
Editor on one, everything else on the other.
Curious about a specific tool or my dotfiles? Open the terminal and type neofetch, or just ask.