The Beginning
It all started in the most unexpected way. I was watching a Korean drama called Vagabond — a show full of intense security operations, hacking scenes, and real tech in the field. Around the same time, I watched a Kenyan movie called Queen Sono, which also had that tech-driven world. Both movies amazed me, but honestly, they didn't push me toward tech directly.
What really pushed me was a simple question I couldn't stop asking myself: "How does this stuff actually work?" How does YouTube stream videos? How do people store all their information online? Everything I saw made me wonder what was happening behind the screen.
So I asked a friend who was studying multimedia to help me figure out how to become a hacker — yeah, that was my goal at the time. He didn't really know much about it, but he gave me his tools: Photoshop, Adobe Premiere Pro, and some of his course materials about creating logos in PowerPoint and other multimedia stuff. I learned those tools, but quickly realized — that wasn't my field.
Then I asked another friend how people hack WiFi passwords. He told me: "They use CMD." That's all I needed to hear. I grabbed my laptop and started searching for videos — how to hack WiFi using CMD, how to hack phones using CMD, anything with CMD and hacking. At this point, I didn't even know what coding was. I had no idea that writing code was even a thing.
The Spark
Then one day, while browsing through all those CMD hacking videos, something appeared in my recommendations — a video by some Indian guy with the title: "HOW TO CODE."
Those three words were completely new to me. I clicked on it, and he explained that if you want to write code, you start with HTML, then CSS, then JavaScript. I had never heard of any of these before. I wrote everything down in my notebook and immediately started searching for HTML tutorials.
The first real tutorial I found was "Building a Website Using HTML and CSS" by Traversy Media. Watching him write code felt like magic. I was completely geeking out. And then came the moment I will never forget — when my HTML file ran "Hello World" in my Chrome browser.
I looked at the screen and thought: "Wait... I can make a website too?"
I followed his tutorial, learned how to create forms and page structures, and then ran to tell my family: "I can build a website!" I was 15 years old. And that's how my journey into tech started.
The Struggle
The hardest part? I was completely on my own. No tutor, no mentor, no one to tell me what to learn next. I was the one setting my own timeline, choosing my own path — and honestly, I got it wrong many times.
I mixed everything up at the start. One day I'd be learning HTML and CSS, the next week I'd jump into C++, then Python, then JavaScript. I was all over the place, not following any proper learning path. There was no ChatGPT back then to guide me — just YouTube tutorials and programming books I'd download.
It was tough. I was mixing things up, not following the right order, and sometimes feeling lost. But my curiosity was stronger than the confusion. That same curiosity that made me ask "how does this work?" is what kept me going — downloading more books, watching more tutorials, writing more code.
And eventually, I managed to get it done. Not perfectly, not the "right" way — but I got it done.
Where I Am Now
Since 2020, I've been a dedicated software developer — and looking back, it's hard to believe how far that chaotic beginning has taken me. What started as a kid trying to hack WiFi through CMD turned into a real career building software that solves real problems for real people.
My first real project was an e-commerce website for a local tech shop. When I saw that site go live and actually help someone run their business, it hit me — that thing that started as chaos is actually turning into something real and beneficial. That moment changed everything for me. It wasn't just about code anymore. It was about impact.
Today, I specialize in backend development, with deep experience in system architecture design and system thinking. I don't just write code — I think about how systems connect, how data flows, and how to build things that scale. I've worked on projects and helped more people solve their real-life business problems through technology.
From websites to mobile apps to full software systems — if someone has a problem and technology can solve it, I want to be the one building that solution.
Giving Back
One thing I never forgot is how hard it was to learn on my own. No one showed me the way — I had to figure it all out by myself. That's why today, I make it a point to help others who are on the same path.
I've tutored students about coding, helped individuals understand how to think about problems before writing a single line of code, and worked with businesses to diagnose and fix real system issues. Whether it's mentoring a beginner or patching a broken production system — I'm still doing it, and I don't plan to stop.
Because at the end of the day, the best part of this journey isn't the code I've written — it's the people I've helped along the way. And I'm proud of that.