📍 Florida · ⚙️ Self-hosted systems builder · 🧱 Alias: dunamismax
I build software that still makes sense at 2am: self-hosted when possible, local-first where it matters, explicit about its tradeoffs, and verified before it gets trusted.
I like software that a small team can actually own.
That usually means:
- infrastructure that is understandable without a priesthood
- tools that help the operator instead of hiding the system from them
- explicit data flow over magic
- local-first and self-hosted setups when control matters
- boring technology where boring wins, and lower-level technology where control is worth the cost
I am not chasing stacks for their own sake. I care about backend systems, networking, devops, self-hosting, control planes, CLIs, TUIs, and infrastructure tools that earn their place by being useful under real operating conditions.
My lane is straightforward:
- Python for operational software, automation, verification, control planes, and practical web tooling
- Go for backend services, infra tools, and network-facing systems where simplicity and performance both matter
- C for systems fundamentals, low-level tooling, and staying close enough to the machine to understand what the abstractions cost
A few repos that represent the kind of work I actually want to keep doing:
- changeledger — operational memory and change intelligence for IT, platform, and ops teams
- verify-patch — patch-aware verification for Python repositories with repo-native checks and operator-friendly output
- scriptspace — a workspace manager for single-file Python scripts built around PEP 723 and
uv - boring-go-web — a practical Go web starter for shipping without framework theater
- c-from-the-ground-up — project-based C learning focused on systems fundamentals through runnable lessons
More Go and C work is coming. The direction is backend, infrastructure, networking, and tools — not toy repos for the sake of having more repos.
- OpenClaw — contributor; currently 2 merged PRs upstream
- Ship small. Verify always.
- Prefer boring infrastructure over clever architecture.
- Make CLI, API, and operator workflows first-class.
- Treat docs as part of the product.
- Optimize for maintenance reality, not launch-day aesthetics.