From Projects to Purpose: My Journey in Tech

My journey with computers started way before I knew what “software engineering” really means.

Back in 7th grade, I had a strong interest in computers and laptops. I loved exploring systems, settings, and just figuring out how things work. At that time, I didn’t know much about coding or programming. I just knew one thing: I enjoy being around computers.

After school, I wanted to go for FSc, but due to low marks, that path didn’t work out. Instead, I took admission in BS Software Engineering. Looking back, that decision changed everything for me.

Learning Beyond the Classroom

College gave me the foundation, but most of my practical skills came from outside.
YouTube tutorials, online courses, bootcamps, and official docs were my real teachers.

I was very curious. I kept asking myself:

• What if I build this?
• What if I try that?
• How does this system actually work?

My first real freelance project was for a South African client, where I worked on a blockchain-based school donation system using crypto. At that time, my confidence was high. I felt like I could learn and build almost anything.

But slowly, reality hit.

The Phase of Chasing Everything

As I moved forward, I realized one hard truth:
Software engineering is a very vast field.

Web apps, mobile apps, dashboards, backend, DevOps, testing, automation, AI — everything looked important. I wanted to learn all of it. And honestly, that mindset was exciting but also very exhausting.

Over time, my confidence went down a bit. Not because I was bad — but because I realized nobody can master everything. Still, my hope never went to zero.

Even today, sometimes I feel lost. Sometimes I feel burnt out. And that’s normal.

Entering the Real World

The real shift happened when I started my job and worked on production-level systems.

That’s where I truly tested my skills.

The corporate and startup world taught me things that personal projects never could:

• Deadlines are real
• Ownership matters
• Responsibility is heavy
• Impact is more important than perfection

I learned that it’s not just about completing tasks or shipping features. It’s about solving real problems, making decisions, and owning the outcome.

This is where my thinking changed.

From Learning Everything to Learning What Matters

At one point, I had to accept something honestly:
Trying to learn everything was not feasible. It was a mad decision.

So I changed my approach.

Now, I focus on learning what actually matters, and then polishing those skills on the go. Instead of chasing every new shiny thing, I focus on depth, fundamentals, and real-world problem solving.

This mindset also shaped how I see AI.

AI, Skills, and Reality

When AI started booming, it made me think deeply about the future of programming and my own skills.

One thing became very clear to me:
AI is powerful, but AI alone is not the solution.

What really matters is:

• Understanding systems from scratch
• Knowing why something works, not just how
• Designing solutions, not just generating code

AI is a tool. Skills are the foundation.
And that foundation cannot be replaced easily.

Where I Am Now

Today, I work more with AI agents, chatbots, and intelligent systems, but my approach is very different from before.

I don’t just build projects to finish them. I build to:

• Solve real problems
• Create leverage with AI
• Deliver impact for businesses and founders

I still struggle with burnout. I still feel tired sometimes, especially when I don’t have enough time to work on side projects outside my job. But now I’m more honest with myself.

I’m no longer chasing random projects.

What I’m Really Chasing

Today, I’m chasing:

• The success of meaningful projects
• And most importantly, my peace of mind

This journey from projects to purpose shaped me not just as a developer, but as a person. I’m still learning, still growing — but now with direction.

And that makes all the difference.