My Journey as a Full Stack Developer — I Never Started for the Job

Written by Haris Malik

“I never started coding because I wanted a job. I started because I loved building things.”

It Started With Curiosity

Long before I knew what software engineering was, I was simply curious.

As a kid, I spent hours trying to understand how apps and games worked. I wasn’t trying to become a developer—I just enjoyed exploring technology.

I remember experimenting with Android customization, modifying games for fun, and trying different tools simply because I wanted to see what was possible. Looking back, I wasn’t learning to “hack”; I was learning to ask questions:

“How does this work?”

That question has stayed with me ever since.

The Day I Wanted My Own Website

At one point, I became obsessed with Dragon Ball.

More specifically…

Goku.

I searched for wallpapers every day, but eventually I thought:

“Why don’t I just make my own website with all my favorite wallpapers?”

That single thought introduced me to HTML.

My first webpage wasn’t beautiful.

There was no CSS.

No animations.

No JavaScript.

Just images of Goku and basic HTML tags.

But seeing something I created appear in the browser felt incredible.

That was the moment I realized…

You can build things from nothing.

CSS Made Everything Fun

Then CSS entered my life.

Suddenly I could change colors.

Move elements.

Design layouts.

Create something that actually looked good.

I still remember copying and rewriting the same website over and over again just because I enjoyed improving it.

Every day I learned something new.

Every day the website looked a little better.

Then JavaScript Humbled Me

HTML was easy.

CSS was fun.

JavaScript…

JavaScript was confusing.

Nothing worked the first time.

Errors everywhere.

Functions.

Events.

Variables.

I questioned myself many times.

But quitting never crossed my mind.

If something didn’t work…

I’d try again.

And again.

And eventually…

It would finally make sense.

Looking back, JavaScript taught me something far more valuable than programming.

It taught me patience.

I Never Had a Mentor

When I started learning, AI assistants didn’t exist.

There was no ChatGPT.

No GitHub Copilot.

No instant answers.

Most of the time it was just:

Google.

Stack Overflow.

Documentation.

And lots of trial and error.

Sometimes I spent hours fixing a single bug.

Today learning is much easier, but I believe struggling with problems taught me how to think independently.

Because of that experience, I always wanted to become the mentor I never had.

Over the years, I’ve helped students who were starting from zero—sharing learning paths, reviewing projects, and encouraging them to keep going when they got stuck.

Seeing someone else gain confidence is just as rewarding as solving a difficult programming problem.

The Biggest Opportunity of My Life

After learning frontend development, I expected my next project to be another website.

Instead…

I was given the opportunity to build a complete Hotel Reservation Management System.

It wasn’t a calculator.

It wasn’t a portfolio website.

It was software that businesses would actually use.

The truth?

I had absolutely no experience building something that large.

I had no idea where to begin.

But one thought stayed in my head.

“Even if I fail, I’ll learn something.”

That mindset changed my life.

Nine Hours a Day

For months, coding became my daily routine.

Sometimes nine hours.

Sometimes more.

I wasn’t building just to finish the client’s project.

I wanted to understand everything.

Why does this feature exist?

How should reservations work?

How do invoices work?

How do permissions work?

How do reports work?

How should payments be handled?

I wasn’t copying software.

I was learning how software should be designed.

Eventually…

The system went live.

Hotels started using it.

Real users depended on it.

That was the moment my confidence changed forever.

Building Software Became My Passion

After the hotel system, building websites felt different.

I realized what excited me most wasn’t landing pages.

It was solving operational problems.

That led me to build:

  • Hotel Reservation Systems
  • Tour & Travel Itinerary Software
  • CRM Platforms
  • Invoice Automation Systems
  • Billing Software
  • Business Management Tools
  • Real Estate Solutions

Some projects were sold as one-time purchases.

Some became subscription-based systems.

Each one taught me something different.

Failure Was Never the End

Not every project succeeded.

Not every idea worked.

There were bugs.

Rejected features.

Missed expectations.

And plenty of mistakes.

But I never hated programming because of them.

In fact…

Those failures taught me more than the successful projects ever could.

Taking Breaks Didn’t Mean Giving Up

There were times when I disappeared from coding.

Sometimes for weeks.

Sometimes for months.

Life happens.

Motivation changes.

Burnout is real.

But every single time…

I came back.

Because coding never felt like an obligation.

It always felt like home.

Even Today…

Even after years of building software…

I still get excited whenever someone says:

“Can we build this?”

That feeling hasn’t changed.

A new problem.

A blank screen.

An idea waiting to become reality.

That’s still my favorite part of software development.

Questions I Get Asked Often

Does a College Degree Matter?

This is only my personal experience.

Degree—don’t ask—but I found that most of my practical software engineering skills came from building projects outside the classroom. What I learned in class didn’t really teach me much either.

College gave me nothing but assignments, exams, and learning that was related to the syllabus—not real-world growth. Real growth happened through curiosity, documentation, experimenting, and building real applications.

For me, projects were the best teacher.

Your experience may be different, and that’s okay.

Will AI Take My Job?

I never learned programming because I wanted a job.

I learned it because I genuinely enjoy building software.

If AI keeps improving, I’ll still be building things.

AI is a tool.

Understanding problems, designing systems, and making thoughtful engineering decisions are still human skills.

Use AI to accelerate your work—but don’t let it replace your understanding.

Where Should I Start?

Don’t start with what’s trending.

Start with what genuinely interests you.

Maybe it’s:

  • Web Development
  • Mobile Apps
  • Game Development
  • Cybersecurity
  • AI
  • Desktop Applications

Interest creates consistency.

Consistency creates skill.

Where Should I Learn?

Today there are countless resources.

Books.

Documentation.

YouTube.

Courses.

AI assistants.

Use them all.

But don’t let AI become your brain.

Learn the fundamentals first.

Write code yourself.

Make mistakes.

Debug them.

Only then will AI become a multiplier instead of a dependency.

What I Believe Today

Looking back…

I don’t think my biggest achievement is any particular project.

It’s the fact that I never stopped building.

Every project taught me something.

Every failure improved me.

Every success gave me confidence.

And every line of code reminded me why I started.

Final Thoughts

I still don’t know exactly where this journey will end.

Maybe I’ll build products used by millions.

Maybe I’ll mentor hundreds of developers.

Maybe I’ll start my own company.

I don’t know.

But I do know one thing.

Tomorrow…

I’ll probably wake up excited to build something new.

Because that curiosity I had as a kid never disappeared.

It simply grew into a career.

“Don’t chase programming because it pays well. Chase it because you can’t stop thinking about the next thing you want to build. Everything else will follow.” — Haris Malik