Full-stack engineer and infrastructure nerd based in Bettendorf, IA (Quad Cities area). I build, ship, and scale things. And I genuinely enjoy doing it well.
I'm currently taking on new clients. If you've got a project, let's talk → alexasaservice.com
I care a lot about reliability. Not in a boring "we blindly follow best practices" way, but in a "this thing runs at 3am without anyone babysitting it" way. Web apps, APIs, DevOps pipelines, cloud infra. Greenfield or legacy, I'm comfortable either way.
Best practices are best practiced mindfully. There's a real difference between making a deliberate architectural decision and reflexively bolting on another framework because it showed up in a blog post. Every tool, pattern, and dependency you add has a cost. Sometimes that cost is absolutely worth it. Sometimes you're just building a katamari ball of abstractions that no one on the team can debug at 3am. Good software is intentional. It respects the environment it's running in, the team that has to maintain it, and the problem it's actually trying to solve.
Languages and tools I reach for regularly:
This account is a mix of work-in-progress tools, fun experiments, and occasional examples worth sharing. More will get cleaned up and added over time.
🦗 Cricket
A deliberately minimal HTTP service for smoke testing deployments, networking, and load balancers. Hit it, watch it respond with hostname + PID + request info, and see exactly where traffic is landing. Has Prometheus metrics built in and zero external dependencies. Small, observable, and useful.
$ curl http://my-app.internal/{
"c": "chirp!",
"h": "web-node-3",
"i": "10.0.1.15",
"r": "/",
"p": 1337
}Chirp · Hostname · IP · Request · PID
Node.js · Docker · Prometheus · GitHub Actions CI/CD


