Network engineer by trade. Photographer by passion. I build free, open-source tools for the problems I actually encounter — from tracking precious metals to auditing switch migrations.
Battle-tested patterns, scripts, and architecture guides from 400+ Claude Code sessions. Free to use, adapt, and share.
Free tools built for real problems — network infrastructure, finance, AI companions, and developer tooling. Every project is where the guides above were battle-tested.
I'm a network engineer who has spent a career building and managing enterprise infrastructure — switches, firewalls, monitoring, the whole stack. When I'm not at work, I'm either behind a camera or behind a terminal, usually solving a problem that bugged me enough to build something about it.
Every project here started the same way: I needed a tool that didn't exist, or the ones that did were too expensive, too locked-down, or too complicated for what should be simple. So I built my own. They're all free. They're all open source.
When I'm not writing code or configuring networks, I'm a photographer. Landscapes, architecture, the occasional portrait — you can find that work at lonniebruton.com.
I build with Claude Code — an AI-assisted development tool. I'm not a software engineer by training, but after two decades in networking and infrastructure, I've learned that the ability to articulate what needs to be built and why matters more than memorizing syntax. If you can think in structured logic and describe what you need clearly, the language is just a detail.
That said, I don't take this lightly. My workflow is built around a year of iteration on human-in-the-loop gates — structured specs, design reviews, and quality checks that ensure every piece of code is intentional and reviewed before it ships. The goal isn't to generate code fast. It's to build tools that are reliable, secure, and actually useful.
Everything here is free and open source because I believe these tools should solve real problems for real people — not generate noise for a quick buck. If something I've built helps you, use it. If you want to improve it, the repo is right there.