WHAT IF?

A question from a curious kid who wanted to know how Minecraft was built slowly became the beginning of everything—coding, breaking things, learning, exploring, and wondering if all of it could someday lead somewhere.

What If This Is Where I Begin?

There was a time when I didn't know what programming was.

I didn't know what a programming language was.

I didn't know what Google was.

I didn't know how people actually made the things I spent hours using.

I was just a kid.

Class 1.

Playing around on a laptop, exploring whatever I could find, clicking things, trying things, breaking things without even knowing I was breaking them.

And then there was Minecraft.

I played it like every other kid did.

But eventually, one question appeared.

"How was Minecraft built?"

I didn't know that question would stay with me.

I didn't know it would become the beginning of something.

At the time, it was just curiosity.

Just a kid wanting to know how something worked.

But sometimes the questions that look insignificant at the beginning become the ones that quietly change everything.

"Curiosity rarely announces what it is going to become."

THE QUESTION

I wanted to know how Minecraft was made.

But I didn't know how to find the answer.

I didn't know programming.

I didn't know where programmers learned.

I didn't even know that Google was something I could use to search for answers.

At that point, YouTube was basically my search engine.

So I searched.

"How to make games."

"How is Minecraft made?"

"How to learn C++."

And somehow, I found myself watching videos about programming.

C++ became one of the first languages I tried to learn.

I didn't have a roadmap.

I didn't have some carefully designed curriculum.

I didn't have a mentor sitting beside me explaining what every line meant.

I had a laptop.

YouTube.

A lot of confusion.

And a question I couldn't let go of.

"I didn't know what I was doing. I only knew that I wanted to know."

Maybe that was enough.

I KNEW ALMOST NOTHING

Starting wasn't difficult because I was afraid.

It was difficult because I didn't understand anything.

Installing things was an adventure by itself.

Setting up environments.

Figuring out what to download.

Understanding what files were.

Understanding what commands were.

Understanding why something that worked in a video wasn't working on my machine.

At one point, I managed to corrupt Windows.

Then I got stuck trying to figure out how to use a Linux distribution alongside Windows.

It wasn't some clean beginning.

There was no perfect setup.

No perfect environment.

No moment where everything suddenly made sense.

There was just one problem after another.

And every problem created another question.

But I kept looking.

Because I hadn't learned enough to know when something was supposed to be impossible.

"Sometimes ignorance is useful. You haven't learned enough reasons to stop."

I DIDN'T KNOW I COULDN'T

I think that's one of the strangest things about starting young.

You don't always understand the size of what you're trying to do.

You don't know how many years it might take.

You don't know how many people are already better than you.

You don't know how complicated the thing actually is.

And maybe that's why you try.

I wasn't sitting there thinking,

"I'm going to become incredibly good at programming."

I was just exploring.

One language.

Then another.

One concept.

Then another.

Different areas.

Different technologies.

Different things that caught my attention.

The beginning wasn't a plan.

It was exploration.

"I wasn't brave enough to begin. I was simply curious enough to continue."

And sometimes, those two things look exactly the same from the outside.

THEN I STARTED EXPLORING

Once I started learning, I didn't stay in one place.

I explored.

Programming languages.

Development.

Different technologies.

Different ideas.

Different things I wanted to build.

Some of them stayed.

Some disappeared.

Some made sense.

Some made absolutely no sense.

But every new thing gave me another piece of the picture.

I wasn't building a career plan.

I was trying to understand what was possible.

And somewhere along the way, I realized something.

I liked the feeling of being able to make something exist.

Something that wasn't there before.

A piece of code.

A website.

A project.

An idea turned into something I could actually interact with.

"There is a particular kind of satisfaction in making something exist that didn't exist before you touched it."

Maybe that's what kept me going.

BUT THERE WAS ALWAYS SOMETHING ELSE

Even then, there was another thought running underneath everything.

Independence.

I had always wanted to grow up quickly.

I wanted to be eighteen.

I wanted a bike.

I wanted money.

I wanted the freedom that came with being able to take care of myself.

I wanted to be independent.

That wasn't necessarily what made me start coding.

The curiosity came first.

But eventually, the two ideas started meeting each other.

I began wondering:

What if these skills could actually take me somewhere?

What if learning this could eventually help me earn?

What if I could build something of my own?

What if I could become independent through what I knew?

And eventually, the question became bigger than Minecraft.

"What if the thing I started out of curiosity could eventually become the thing that gives me freedom?"

I didn't know the answer.

I still don't know the complete answer.

But I wanted to find out.

WHAT IF?

That's probably where this story really begins.