I didn't plan to become a software engineer.
I didn't plan to become a software engineer.
I've always been interested in computers, but for a long time, I never really thought about programming as something I would pursue seriously.
That changed back in my senior secondary education.
One day in my school's ICT lab, I noticed a friend watching a Bro Code HTML tutorial. I was curious about what he was doing, so I started watching too. That curiosity eventually pushed me to try HTML for myself.
Then came CSS. Then JavaScript.
And somewhere along the way, I fell in love with programming.
I started exploring React, Node.js, React Native, databases and the MERN stack. I didn't have some perfectly planned roadmap — I mostly learned by building things, breaking them, figuring out why they broke, and trying again.
I actually started programming around 15, but I wasn't particularly serious about it at first. Over time, though, something changed. I started taking it seriously and realized that this was something I genuinely wanted to pursue.
The more I learned, the more I became obsessed with one idea:
I can actually build things that people use.
Software gives me the ability to take an idea that exists only in my head, turn it into something real, and potentially make someone's life easier.
That's what keeps me interested.
I don't just want to write code for the sake of writing code. I want to understand problems, build solutions, and eventually create products that people genuinely find useful.
That's also why I decided that my long-term goal isn't just to become a software engineer.
I want to become a software engineer and entrepreneur.
I believe combining those two sides — being able to build the technology and understand the problems worth solving — can give me the ability to create things that actually matter.
Earlier this year, I joined the founding team of Pantheon, a venture studio we're building from the ground up.
It's been a completely different experience from just building personal projects. I'm learning what it means to work with other people, think about ideas beyond the code, and try to turn something into an actual venture.
I'm still early in that journey, but that's part of what makes it exciting.
Then AI started changing the software industry.
I'll be honest — seeing how quickly AI is evolving made me question the traditional software-engineering path for a while.
But eventually I realized something important:
Software engineering has never been only about writing code.
It's about understanding a problem, designing a solution, building it, testing it, and making it useful.
AI doesn't change that. If anything, it gives me more tools to build.
That's why I've recently started learning Python and exploring AI and automation — not because I'm abandoning software engineering, but because I want to become better at using technology to solve problems.
I'm also starting a YouTube channel to document this journey.
I want to share what I'm building, what I'm learning, the things that don't work, and hopefully some of the lessons I pick up along the way.
I'm still figuring things out, so the channel isn't going to be me pretending I have everything mastered.
It's simply me building, learning, and documenting the journey.
If you're interested in following along, feel free to subscribe.
I'm still a student. I'm still learning. I haven't built a long list of client projects, and I definitely don't have everything figured out.
But I'm building.
I'm learning.
I'm experimenting.
And I'm trying to get a little better every day.
My goal is simple:
Become a great software engineer, build meaningful products, become an entrepreneur, and use technology to solve real problems.
This is only the beginning.