Go backend engineering
Typed Go services behind HTTP with explicit contracts — provider-aware WebSearch, SSRF-guarded WebFetch, explicit caching and degradation, and observability.
Evidence: SearchX ↗ Evidence: GoHOME — hand-written Redis ↗No arbitrary progress bars. Each group describes the kind of behavior I can build and points toward observable work.
Typed Go services behind HTTP with explicit contracts — provider-aware WebSearch, SSRF-guarded WebFetch, explicit caching and degradation, and observability.
Evidence: SearchX ↗ Evidence: GoHOME — hand-written Redis ↗Type-safe browser interfaces that render streaming state and stay decoupled from backend domain models.
Evidence: Runtime Inspector ↗Deploying and operating services on a self-hosted single-node cluster (minikube) — Deployments, Secrets, hostPath storage, container images, and Cloudflare tunnels.
Evidence: SearchX ↗Typed event-driven systems — domain events, pure decision functions, reducers, actors, Tokio async, and effect execution.
Evidence: Looper ↗Four years of ArchLinux as a daily desktop and server platform — KDE and Hyprland (end-4 dotfiles), rolling-release maintenance, systemd services, packaging, and dotfile-driven configuration.
Evidence: dots-hyprland (end-4 reference) ↗Ongoing architecture research on agent runtimes — extension models, out-of-process plugins, trace-first observability, and the harness/product boundary.
Read the design principles ↗