BUILD

What Happens When You Actually Build Something?

There is a difference between knowing something and making something with it.

For a long time, I was learning.

Learning languages.
Learning frameworks.
Learning how things worked.
Learning how to solve problems.

But eventually, learning stopped being enough.

I wanted to make something.

Not because someone asked me to.

Not because I had an assignment.

Not because I needed a certificate.

I just had this feeling from the beginning:

“I want this to exist.”

And once that thought gets into your head, learning starts to feel different.

You stop asking only “What can I learn?”

You start asking:

“What can I make?”

THE FIRST THING WE BUILT

The first thing I remember actually building wasn't something I built alone.

It was in middle school.

My best friend and I built DAV Notes — a platform for providing notes to students in our school.

It wasn't some massive startup.

It wasn't technically extraordinary.

It wasn't going to change the world.

But it was ours.

We had an idea.

We had a problem.

We wanted something to exist.

So we built it.

And I think that was one of the first moments where coding stopped being something I was learning and became something I could use to create something real.

That distinction mattered.

Because when you're following a tutorial, the person who made the tutorial already knows what the final result should look like.

You don't.

You're following a path someone else already walked.

Building is different.

There is no guarantee that the path exists.

“Learning gives you knowledge. Building forces you to find out what that knowledge is actually worth.”

DAV Notes wasn't perfect.

Neither were we.

But it existed.

And sometimes, that's the moment everything changes.

IT WAS NEVER JUST HAPPINESS

Building things at the beginning was a strange experience.

It was frustrating.

It was exciting.

It was irritating.

It was satisfying.

Sometimes I was happy.

Sometimes I was annoyed.

Sometimes I wanted to throw everything away.

Sometimes I couldn't stop thinking about it.

I was obsessed.

I think that's what made the difference.

I didn't build because building was always fun.

I built because I wanted the thing in my head to become real.

And when reality didn't match what I imagined, I wanted to fix it.

Then I would break something else.

Fix that.

Find another problem.

Fix that.

Get frustrated.

Try again.

And somewhere inside that cycle, I started realizing something:

Building isn't about avoiding problems.

Building is creating enough problems that you're willing to solve.

I WANTED THINGS TO EXIST

Over time, I started building things that nobody had asked me to build.

Sometimes they were for productivity.

Sometimes automation.

Sometimes they solved a problem I personally had.

Sometimes they were just ideas that appeared in my head.

And sometimes there wasn't even a particularly good reason.

I just wanted them to exist.

That feeling is still there.

Even today, there are things I look at and think:

“I want this to exist.”

And then I start thinking about how I could make it happen.

Maybe I don't have the skills yet.

Maybe I don't have the time.

Maybe the idea is bigger than what I can currently do.

Sometimes I build it.

Sometimes I don't.

Some things get finished.

Some things stay unfinished.

Some disappear completely.

But the instinct remains.

Make it real.

“A builder doesn't always start with the ability to create the idea. Sometimes they start with the refusal to leave the idea imaginary.”

THEN IT BECAME SERIOUS

There was a different feeling when I got my first client.

Someone came to me and asked me to build a web application.

That was different.

Until then, a lot of what I built existed because I wanted it to exist.

Now someone else was trusting me to make something exist for them.

Suddenly, it wasn't only about whether I liked what I made.

Someone was depending on it.

Someone had expectations.

Someone had a problem.

And I had to solve it.

That was probably one of the first times I thought:

Okay. This is serious.

It changed the relationship I had with building.

A personal project can fail quietly.

A client project teaches you that someone else might be waiting for the result.

“The moment someone depends on what you build, craftsmanship stops being optional.”

That responsibility was different.

And I liked it.

WHAT IF I DON'T KNOW HOW?

This became one of the most useful things I learned.

Eventually, every project reaches the same point.

You know what you want.

You know some of the things required.

And then you reach something you have absolutely no idea how to do.

Earlier, that might have felt like a wall.

Now, I see it more like a map.

First, I cover everything I can do.

Then I map the entire problem.

I separate what I understand from what I don't.

Then I look at the things I can't currently do.

And I start investigating.

I use AI.

I ask professionals.

I try to figure things out myself.

I read.

I experiment.

I make mistakes.

I find out what's still missing.

And then I learn that part.

Then I build.

It's not:

Learn everything → become ready → build.

It's more like:

Build → discover what you don't know → learn it → build again.

“You don't need to know everything before you start. You need to know how to find what you don't know.”

That changed everything.

Because there will always be something I don't know.

THE THING I COULDN'T BUILD

There is another side to this.

Sometimes you want something to exist so badly that you try to make it happen.

And sometimes you can't.

I've had projects like that.

Things I wanted to build but couldn't.

Sometimes I eventually figure them out.

Sometimes I leave them where they are.

I used to think leaving something unfinished meant I had failed.

I don't always think that anymore.

Sometimes the project simply showed me the distance between what I wanted to build and what I was capable of building at that moment.

And that distance is useful.

Because now I know where I need to grow.

“An unfinished project is not always wasted effort. Sometimes it is a measurement of the distance between your ambition and your current ability.”

That distance doesn't have to stay there forever.

THEN I STARTED BREAKING THINGS

This is where my story gets a little strange.

I started building seriously.

And somewhere along the way, I started wanting to break things.

Cybersecurity.

I wanted to know whether I could actually hack.

Whether I could pentest.

Whether I could find weaknesses in systems.

At first, there was a very simple question behind it:

Can I do this?

So I tried.

I explored systems.

I tested things.

I looked for weaknesses.

I made mistakes.

Sometimes I found something.

Sometimes I didn't.

Sometimes I proved to myself that something I thought I understood was actually much more complicated.

And eventually, I realized something important.

Building and breaking weren't opposites.

They were teaching me the same thing from different directions.

Building asked:

How do I make this work?

Breaking asked:

Why does this work — and where does it fail?

I STARTED THINKING IN SYSTEMS

Cybersecurity changed the way I build.

I started thinking in systems.

I started breaking large problems into smaller ones.

I became more patient.

I stopped being as afraid of not knowing.

I started caring more about the person actually using what I built.

And I became more interested in why something worked.

Not just:

“What code do I write?”

But:

“What is actually happening here?”

That question follows me now.

When I build something, I want to understand it.

When I break something, I want to understand why it broke.

When I see a system, I want to understand what is underneath it.

And that curiosity keeps pulling me deeper.

“Building teaches you how to create a system. Breaking teaches you how much of that system you never understood.”

I THOUGHT I COULD BUILD ANYTHING

There was a time when learning to code gave me a strange kind of confidence.

I thought:

I can build anything.

And honestly?

I was wrong.

Not because I can't build.

Because there is far more to learn than I knew existed.

The more I build, the more I realize how much I don't know.

There are technologies I haven't touched.

Systems I don't understand.

Problems I wouldn't know how to approach yet.

Things that require years of experience.

Things that require other people.

Things that require knowledge I haven't earned yet.

And surprisingly, I don't find that discouraging anymore.

It makes the world bigger.

Because every time I discover something I don't know, I also discover another direction I can go.

“The deeper you go, the larger the unknown becomes. That isn't evidence of failure. It is evidence that you've finally started looking closely.”

SO WHAT AM I?

Developer?

Cybersecurity enthusiast?

Builder?

Security researcher?

Someone who likes taking things apart?

Someone who likes creating them?

I don't really know.

Maybe I don't need to choose.

Because to me, building isn't coding.

Building is making something come alive.

A fantasy.

A project.

An idea.

A system.

A tool.

Hardware.

Software.

A product.

Even something I eventually want to understand deeply enough to break.

Sometimes building means writing code.

Sometimes it means designing.

Sometimes it means researching.

Sometimes it means learning for weeks before writing a single useful line.

Sometimes it means taking something apart just to understand how it works.

The medium changes.

The instinct doesn't.

Make it exist.

I'M STILL LEARNING

The biggest thing building taught me wasn't how to build.

It was how little I actually know.

When I first learned to code, I thought knowing how to write code meant I could create anything.

Now I understand it differently.

I know.

But I don't know beyond that.

And there is a strange comfort in admitting that.

Because I'm still learning.

Still building.

Still breaking.

Still figuring things out.

Still finding things I can't do.

Still learning how to do them.

Still finding better ways to build the things I already know how to make.

And maybe that's what a builder really is.

Not someone who knows how to build everything.

But someone who sees something that doesn't exist and thinks:

“I wonder if I can make it real.”

Then starts figuring it out.

BUILD

What Happens When You Actually Build Something?

You discover that knowing isn't enough.

You discover that your idea will always be bigger than your current skill.

You discover that some things will work.

Some won't.

Some will be finished.

Some will be abandoned.

Some will become something completely different from what you originally imagined.

You discover clients.

Deadlines.

Frustration.

Responsibility.

Curiosity.

Failure.

Cybersecurity.

Systems.

And eventually, you discover something more uncomfortable:

The more you build, the more you realize you still have to learn.

I don't think that's a problem anymore.

I think that's the point.

Because I'm not finished.

I'm not even close.

I know what I know.

I don't know what I don't know.

And somewhere between those two things—

I'm still building.