Why I built waxthe.dev — and what this blog covers
June 2, 2026 · by Wax
I do a lot of unrelated-looking things. I run a serious-roleplay FiveM city with a few hundred players and a custom resource library. I hand-code websites for local service businesses. I wire AI into products and internal tools. And I keep writing small desktop utilities to fix problems the “proper” tools ignore.
For years that was scattered across Discord servers, Tebex pages, GitHub repos and my own head. waxthe.dev is the hub — one place that says here’s what I build, here’s how it works, and here’s the proof it runs in production. This blog is the working half of that.
What this blog is not
It’s not SEO filler and it’s not rewritten documentation. I already keep a separate set of evergreen guides for the “how do I do X” questions — server setup, QBCore vs Qbox, lag fixing. Those are reference. The blog is the opposite: dated field notes about what I’m actually shipping this month, including the parts that went sideways.
What you’ll find here
FiveM engineering. Streaming-asset optimization, server-authoritative script design, dispatch and inventory integration — the unglamorous work that keeps a busy city stable.
Hand-coded web. Why I still write static sites by hand in 2026, how I keep them fast, and what that buys a small business versus a page-builder.
AI that does something. Real integrations — whitelisting bots, retrieval over private data, Claude-API workflows — not demos that fall over the second a real user touches them.
Tooling. The C# and Python utilities I build when the ecosystem hands me a problem and no fix.
The bias: everything here runs live
The rule I hold myself to is simple — I don’t write about a technique until I’ve shipped it somewhere real. My FiveM posts come from a live city, not a blank test server. My web posts come from client sites in production. That’s the whole value of reading a builder instead of an aggregator: you get the gotchas, not just the happy path.
If any of it maps to something you need built, that’s not a coincidence — most of what I write about is a product or a service I offer. But you don’t owe me anything to read along. Grab the RSS feed and I’ll see you in the next one.