The story so far
About me
I’m Halis. I’m 17, I write code for a living, and it’s all because I was nosy about how games worked.

When I was 14 I stopped just playing games and started opening them up. I read game clients, picked apart obfuscated bytecode and studied network protocols until the whole thing made sense. I wanted to know what was going on underneath.
That curiosity turned into skills faster than I expected. I taught myself Lua first, then Python, then JavaScript. Not from courses. I needed something to exist, so I learned whatever it took to make it. By 15 I had shipped automation tools and an obfuscation engine that people used every day.
These days I split my time between three things: scripting, security and interface design. They look unrelated, but they feed each other. Knowing how people break software makes me write it differently. Knowing how people behave on a screen makes me design it differently.
Horizon Hub V11 (2026) is where all of that ended up — rebuilt from Nova Hub (2025). It started as a personal experiment, and now thousands of people use it, with a community around it. I built it alone, from the ground up, and I’m not planning to stop.
How I learn: I pick a real problem, build the smallest thing that could work, then break it until I understand it. Docs, source code and network logs first — tutorials only when I’m stuck.
What I care about
Speed
If something feels slow, people notice before they can say why. I try to make things fast first and clever second.
Security
I assume someone will try to break whatever I build, because I’ve been that someone. So I build with that in mind from the start, not as a patch at the end.
How it feels to use
I like interfaces that stay out of the way. Before I think about colors, I think about where a person’s eyes go and where they’d get stuck.
In short
- Clean code I’d be happy to hand to someone else
- Security thought about from day one
- Design based on how people really behave
- Fast delivery, with updates along the way
A normal day
Mornings
School first. I check messages in small gaps — Horizon Hub reports, client updates — but I don’t start anything big before noon. Small fixes go out early so nothing sits broken for a day.
Afternoons
Homework, then deep work. New features, new scripts, or interface builds. One thing at a time, phone face-down, no half-finished tabs. I keep a short list of three things max — if everything is priority, nothing is.
Evenings
Testing, breaking my own protection, reading other people’s code to see what I missed. Evenings are also when the community is awake, so support and shipping mix together.
Exam weeks
Twice a term, school wins and I say so upfront. Shipping slows, messages get shorter, but nothing silently dies — I tell people what to expect before the quiet week, not after.
Outside the code
I’m 17, so school is still part of the day. Mornings and middays belong to classes — code happens in the gaps and in the evenings. It sounds limiting, but it taught me to plan: I keep a short list, pick one thing, and finish it before opening anything else.
I still play games, not just pull them apart. Playing keeps me honest — I feel the lag, the confusing menu, the bug I’d otherwise only read about in a report. Some of my best fixes started as “this annoyed me while playing last night.”
When I code I usually have music on, and when I’m stuck I go for a walk instead of staring harder. Most hard bugs I’ve solved surrendered somewhere away from the keyboard.
I work alone by choice. It means you talk to the person who writes the code, and I stay responsible for everything I ship.
My setup is deliberately boring: a quiet corner, headphones on, one project open. No fancy rig stories — the work is the interesting part, not the desk.
Want the year-by-year version? Read my journey, or see what I’ve built.
Things I believe
Boring wins
Simple code, short lists, early nights before releases. The flashy stuff is fun to read about; the boring stuff is what keeps thousands of users happy.
Say it early
Bad news gets worse with waiting — a late feature, a slow exam week, a bug I can’t fix yet. I’d rather tell you on day one than apologize on day ten.
Rest is a feature
I’ve shipped tired and I’ve shipped rested, and I know which one holds up. One full day off a week, no exceptions — the code is better for it.
Stay curious, stay kind
Everyone in my community was a beginner once, including me at 14. No stupid questions, no showing off — just figuring things out together.
When I’m not shipping
Playing, on purpose
Same games I build for, but with the debugger closed. If the menu confuses me as a player, it’ll confuse everyone — that’s free user research.
The community
Horizon Hub’s Discord isn’t just support tickets. I hang out there, hear what people actually want, and sometimes get feature ideas I’d never have alone.
Rabbit holes
How does this obfuscator work? Why is this API slow? I’ll lose an evening to a question nobody asked — and it usually pays off months later.
Two languages
Turkish at home, English everywhere online. All my docs, code and client talk are in English; all my jokes are better in Turkish.
Sound on
Soundtracks and lo-fi while I build, silence while I debug. Music is a load-bearing part of my setup — the day it’s off, something is wrong.
Reading for fun
Changelogs, postmortems, other people’s source code. Most developers read docs to solve a problem; I read them the way other people read novels.
Good to know
- Student first on school days — code second, and I’m upfront about it
- Async-friendly: clear messages over meetings, any time zone
- Discord-first, English or Turkish, usually replies within a day
- No agencies, no middlemen — you always talk to me directly
Where this is heading
Short term: Horizon Hub V12 — better onboarding, clearer docs, deeper per-game profiles. Keep the thing thousands of people use getting quietly better.
Mid term: more client web apps and interfaces. I like the mix: my own product plus other people’s problems.
Long term: go deeper on security and systems — Rust, reverse engineering, the stuff that takes years. I’m 17; I’ve got time, and I plan to use it.
What I’m not chasing: follower counts, hype launches, or growing just to say a bigger number. If Horizon Hub helps 65 games’ players today, V12 should help them better — not louder.
If any of that sounds like your project, let’s talk.
Want to work together?
Tell me what you’re building, or what’s broken. A few lines is enough. I’ll reply on Discord.
Send a messagePrefer Discord?