What I work on:
- Building and shipping APIs & backend services
- Data pipelines — from ingestion to something useful
- CLI tools & automation — small things that compound
Python gets ideas off the ground; Go is where they go to live. I'll reach for whatever fits, but I start with what's boring and proven.
My default approach: get the most out of the simplest solution first. Bootstrap, jerry-rig, validate — then decide if complexity is actually earned. It usually isn't.
I think code is read more than it's run, and systems are operated by people more than they're executed by machines. That shapes how I write both. Observability and readability aren't nice-to-haves.
Developer convenience compounds quietly. A small automation that removes friction from someone's day is worth more than it looks on paper.
Running NixOS, Neovim, and a tiling WM. Spent probably too long getting my environment to work the way I think — not the other way around. Don't regret it.
Cautiously watching "move fast" meet AI culture. Both are useful tools on their own. Together, at this pace, I think we're making the worst of both.
Stack: Python · Go · Linux · Neovim · NixOS
- sacharya.dev — personal site and portfolio
- nixos-config — NixOS, Neovim, tiling WM, and everything else