My journey into tech didn't start with textbooks — it started with curiosity.
As a kid, I was obsessed with how games worked under the hood. Not just playing them — wondering how the physics, graphics, and logic all came together. That obsession slowly grew into something bigger: a need to understand the "why" and "how" behind every system I touched. That's what led me to Computer Science.
People often ask me:
"Why are you still learning to code when AI does everything now?"
My answer:
"Because I don't just learn to code — I solve. And problem-solvers are never out of a job."
That mindset led me to Automation — building tools to eliminate repetitive work, to think smarter, not harder. And now I'm diving into AI and Machine Learning, combining that same automation instinct with intelligence: systems that learn, adapt, and make lives simpler.
The CS degree wasn't just a curriculum.
It became a certification of freedom —
The freedom to build ideas, launch startups, freelance, collaborate, and solve real problems.
It gave me the keys to an open world, where my logic becomes reality.
Every step — from gaming curiosity to automation to AI — has been driven by one goal:
👉 Understand how things work. Then build something better.
My first "I actually built this" moment didn't come from a tutorial.
It happened in Algorithm Design, first year. Our professor had one rule: no hand-holding, no hints — just problems and your brain. While others complained about the difficulty, I saw it as a challenge. It was the first time I felt completely responsible for finding a solution — and that feeling of ownership changed how I approach everything.
By third year, something bigger clicked.
I used to think Computer Science was just about flashy domains — AI, frontend, backend. But the deeper I went, the more I realized: CS is a whole universe.
Networking. Cryptography. Operating Systems. Compilers. The invisible layers that make everything run — layers most people don't even know exist. It's not just about writing code. It's about understanding how computers think, communicate, and trust each other at every level.
That realization made me fall in love with the depth of this field, not just the surface.
What I've seen so far is just a drop. There's an ocean out there — and I intend to explore it. 🐸
Someday, I want to build a game inspired by Pokémon Fire Red —
Simple, pixelated on the surface.
But underneath: complex NPC behaviors, real-time decisions, layered AI.
A game that's much more than it looks.
That's the kind of work I'm drawn to — things that look simple but have serious depth behind them.
On AI-assisted coding:
I leaned into AI tools heavily for a while — they're fast, and this world moves fast. But I noticed I was starting to skip the thinking. So I course-corrected. Now I use them to accelerate, not to avoid the problem.
Tools should sharpen your edge, not replace it.
On perfectionism in the real world:
Early on, I'd spend hours polishing code — optimizing things nobody asked for, while the actual goal waited. My mentors called it out. That's when I internalized something important:
In the real world, delivering value on time beats writing perfect code every time.
I still care deeply about clean, well-structured code. But now I lead with impact and optimize after.
Somewhere along the way, I stopped thinking of myself as just a developer.
I want to create — tools, systems, maybe a game, maybe a startup.
Something that solves a real problem, or makes something hard feel effortless.
Every bug, every late night, every refactor — it's all part of the same journey.
And I'm just getting started.
Want to build something together? Let's connect.