I like building tools, servers, apps, and random projects that solve problems I actually have.
If I go looking for something and the right tool doesn't exist, there's a pretty good chance I'll just build it myself.
I use AI heavily while developing — call it vibecoding, AI-assisted development, or AI slop if you really want to.
The important part to me is the result.
I don't throw a prompt at an AI and upload whatever comes out. I iterate, test, debug, redesign, break things, fix them again, and keep going until the project is something I'd actually want to use.
If you hate anything made with AI on principle, that's fine — you can leave.
You might be missing out though.
Chances are you wouldn't have known if nobody told you. :)
🌐 Endlink
A Velocity-style proxy for Minecraft Bedrock / Endstone / BDS.
One connection, multiple backend servers, backend switching without reconnecting, failover, forced hosts, permissions, an addon API, and more.
Basically:
Endstone is Paper → Endlink is Velocity.
Related:
- EndlinkGuard — secures backend servers behind Endlink
- ViaEndlink — experimental Java Edition support for Endlink
An Android app made because I wanted a proper "Save to Downloads" option in the share sheet.
It handles files, photos, documents, shared text, and even has a yt-dlp based download flow with quality selection, audio extraction, notifications, history, and more.
A good example of:
"why doesn't this already exist the way I want it?"
followed shortly by:
"fine, I'll make it."
Runs Pygame games headlessly on a server and streams them into an HTML5 canvas over WebSockets, while sending keyboard and mouse input back to the game.
Because apparently putting Pygame in a browser wasn't unreasonable enough.
Firmware and software for a little ESP32-S3 handheld.
Includes a standalone/offline build with a bunch of built-in games and a more advanced server-backed version.
Yes, I actually named a repository robodeck-ai-slop.
My development process is basically:
idea → prototype → break it → fix it → add way too much → polish it → actually use it
AI is a tool in that process, not the quality standard.
I care about:
- things actually working
- sensible architecture
- edge cases
- good configuration
- documentation
- security where it matters
- making projects pleasant to actually use
- polishing the boring parts instead of stopping at the demo
A project being AI-assisted doesn't excuse it being bad software.
A lot of:
Java · Python · Kotlin · TypeScript · Minecraft Bedrock · Cloudburst · Endstone · Android · ESP32 · WebSockets · FastAPI
…and whatever else the next project happens to need.
If the tool I want doesn't exist, I build it.
Sometimes that's a tiny utility.
Sometimes I accidentally build an entire proxy server.
That's the fun part.