I build small, sharp tools — CLIs, automation scripts, and the occasional AI-assisted utility. More interested in how systems actually work than in following a framework's happy path.
I'm working toward a systems- or network-oriented engineering role, coming at it from the tooling side: PowerShell modules, CLI utilities, and cross-language experiments in Rust, Go, TypeScript, and Perl. I like understanding a tool from first principles before reaching for an abstraction, and I'd rather ship one thing that does its job well than three that half-do it.
Lately that's meant building an MCP server, an AI-assisted CLI, and picking through how different front-end frameworks handle the same problem — mostly to see where the abstractions actually earn their keep.
A PowerShell module that finds and loads tab-completion scripts
installed by Scoop, which doesn't
surface them on its own. The interesting part was performance —
recursing Scoop's apps directory picked up duplicate
completions from every installed version of a package, since each
app folder has a current junction pointing at the active
version alongside the real versioned folders. Targeting
apps\*\current directly instead of the whole tree fixed
the duplicates and was dramatically faster once I stopped fighting
PowerShell's wildcard path resolution.