Started with curiosity
2017. I was 13, picking up programming on my own - first HTML/CSS, then real languages, then Lua because I couldn't stop playing Roblox and wondered how the games actually worked. The "make a game" loop hooked me hard.
I started coding in 2017, when I was 13. Years later I'm a software engineer who builds performance-critical Roblox systems - gameplay, multiplayer, optimization - for indie studios, Roblox creators, and teams that need a serious build done right. I care about code that runs fast and survives real players.
2017. I was 13, picking up programming on my own - first HTML/CSS, then real languages, then Lua because I couldn't stop playing Roblox and wondered how the games actually worked. The "make a game" loop hooked me hard.
Years of building things that crashed, datastores that lost data, sloppy systems I had to rip out and redo. That's how I learned what production code actually looks like - every edge case I now anticipate is a scar from something that went wrong once.
I build Roblox games, web apps, and dev tools for paying clients. I keep scope honest, deadlines real, and the code is something the client can actually maintain after I hand it over. No black boxes, no surprises.
The tools I reach for first, grouped by how often they show up in actual paid work - not a wishlist.
Live data from Discord and Steam - what I'm doing, listening to, or playing right now.
The best work happens after midnight. Mornings are for replies and code review.
Games are why I started writing code. They still inform how I think about UX.
Loud guitars on my headphones is the default focus state. Lo-fi for debugging.
The country, not the US state. GMT+4. Most clients are 6–10 hours behind.
Every technique I use came from a tutorial, a forum post, or breaking something.
I'd rather ship a v1 you can actually play than a v3 still in design review.
Things clients usually want to know up front.
Everything runs through my Discord server. Join, tap "Place an Order", and fill in a 30-second form. A private channel opens just for you and me, where we confirm details and I build your project - with automatic live updates every time I push a new version.
It depends on scope. A self-contained system is usually 1-3 days, a medium feature set 1-2 weeks, and a full game or large system a month or more. You get a realistic timeline before any work starts - I'd rather quote honestly than overpromise.
It scales with scope and complexity. Place an order on my Discord server with what you want, your budget, and your deadline - I'll confirm a clear price in your private channel, with no vague ballparks and no surprise add-ons later. A 50% deposit locks in your slot; the rest is due on completion.
Yes - revisions within the agreed scope are included, and I fix any bugs in delivered work free for 48 hours. Out-of-scope changes are priced separately so the line stays clear for both of us.
Discord, exclusively. Every order gets its own private channel where the whole project lives - requests, updates, revisions, and delivery. You get straight answers plus automatic notifications every time your build goes live, not status-update theatre.
Yes. I'll read your code, fix bugs, add features, or rip out and rebuild the parts that don't scale. Share the repo and I'll tell you honestly what it needs.
Always. Everything I write is delivered readable, structured, and yours to use and modify in your own projects - your team can maintain it without me. No black boxes, no lock-in. Reselling or repackaging the work as a product isn't included; see the Terms of Service.
LET'S TALK
Ordering happens on my Discord server: tap "Place an Order", fill in a 30-second form, and you get a private channel with me. I usually reply within 24 hours.
By placing an order you agree to the Terms of Service.