This is not a linear success story. It is a trial-and-error learning journey powered by curiosity, experimentation, and the willingness to break things.
I was introduced to Python at age 9. I didn't understand most of it — variables felt abstract, loops were confusing, and functions made no sense. I couldn't build anything real. But underneath the confusion, something important happened: I realized that computers follow instructions, and I wanted to be the one writing those instructions.
I didn't make progress in Python. But I made progress in curiosity — and that mattered more.
Code.org was the turning point. Drag-and-drop blocks stripped away syntax and let me focus on pure logic. For the first time, I understood what an algorithm actually was — not as a word, but as a way of thinking. Sequences, conditions, loops — they weren't abstract anymore. They were tools I could use.
This phase taught me that understanding comes from doing, not from reading definitions.
Scratch turned coding from a learning exercise into a creative outlet. I built small games, interactive stories, and animations — experimenting with sprites, events, broadcasts, and game loops. The feedback was instant: I could see my code come to life on screen.
This was the first time I created something other people could actually play. That feeling — "I made this" — became addictive.
Unity was a massive jump. The interface alone was overwhelming — panels, inspectors, scenes, prefabs. C# felt alien compared to block-based coding. I spent more time lost in menus than actually creating gameplay. I broke things constantly.
But I kept going. Slowly, I started understanding game loops, UI interaction, and basic physics systems. The frustration wasn't a sign to stop — it was the price of learning something real.
There were moments I paused completely. Lost motivation. Jumped between tools without finishing anything. Started projects and abandoned them. Felt like I wasn't making progress.
Looking back, these breaks weren't failures. They were part of figuring out what I actually wanted to build, and what kind of developer I wanted to become. Sometimes you need to stop to find direction.
Discovering AI-assisted coding changed my entire workflow. Instead of getting stuck on syntax for hours, I could describe what I wanted to build and iterate rapidly. I could prototype ideas in minutes, debug problems faster, and learn new concepts by building real things — not by watching tutorials.
AI became a thinking accelerator. It didn't replace my understanding — it amplified it. I still write code manually, I still understand what every line does. But now I can move at the speed of my ideas.
I dove deep into HTML, CSS, and JavaScript. I launched my first real website — gizlibilgi.com, a reflex brain-training game. Then came bigger projects: Qvelly (a full-stack date tracker), Corridoom (a sandbox FPS with 60+ levels), and Lingorify (a team language-learning platform).
I integrated Firebase for authentication and databases, and started porting web projects to Android using Android Studio. The scope of what I could build expanded rapidly.
Creativity doesn't stop at code. I started making music — exploring sound design and composition as another form of expression. At the same time, I returned to Unity with a much stronger foundation and clearer vision.
This phase represents a shift from "learning to code" to "using code as one tool among many" to create things. Games, websites, apps, music — they're all connected by the same drive: building something from nothing.