Independent. Bare metal Linux. Go programming.

The through-line across everything I do is a conviction that modern systems are over-abstracted by design — and that real ownership of a machine means understanding what each layer is doing and why. My interest is in tools that do one thing and do it directly. No wrappers, no GUIs where a terminal works, no abstraction layers I don't control.

I use ffmpeg, not OBS. I run SLMs by pinning cores and calling llama.cpp directly, not through Ollama or Jan. I'd rather understand a tool at its lowest level than be managed by an interface built around it. I'm learning Go because it fits that approach — small binaries, no runtime dependencies, compiles to a single static file that runs anywhere Linux runs.

The same skepticism I apply to software layers I apply to AI models — I don't take capability claims at face value, I test them. I write about AI model behavior, SLM limitations, and what these systems actually do at the layer below the chat interface: logic traps, hallucination prompts, contradiction detection. Most people use one model for everything and never find its edges. I'm interested in the edges.

I'm a FOSS and Right to Repair advocate. Active in hardware restoration and rescue — returning aging or broken machines to productive use through careful diagnosis, component-level reasoning, and lean purpose-built Linux environments. I work at the intersection of software configuration and low-level hardware communication: driver tuning, display server, audio pipeline, system optimization on Debian-based minimal setups.

I build Linux utilities in Go and Bash. Diagnostic tools, hardware probes, system automation — the kind of thing you drop on an old machine and run without installing anything.

Stack: CrunchBang++ / Openbox / tint2 — Go, Bash — static binaries, bare metal, no unnecessary dependencies.

Posts