Who I Am, How It All Started… and Why This Blog Exists

Introduction

Let me take you back to a very specific moment…

Late 90s. A computer powered on. That familiar startup sound. The Windows 98 loading screen.

For most people, just another machine.

For me?

It felt… magical.

Now let me ask you something:

Do you remember your very first interaction with a computer?

Because I remember mine like it was yesterday.

And that’s where everything started.

How it all began (before code was even a thing for me)

I got my first computer in ‘98.

And honestly, I had no idea what that thing was capable of.

But there was something there.

Something that grabbed my attention in a different way.

At first, it was simple.

Hours in Paint. Drawing random stuff. No goal whatsoever.

But think about this for a second…

Nobody stares at a screen for hours for no reason.

Something starts to spark.

Curiosity crept in slowly.

“What happens if I click this?” “What if I change that?”

And before I realized it…

I was poking around everywhere.

Opening random things. Messing with the system without really understanding it.

And of course…

Breaking stuff too. 😄

There’s one moment that never left my mind.

I’d open CMD. Type help.

And suddenly… a flood of text would fill the screen.

To me, that wasn’t just a command.

That was power.

And then came the best part…

I’d call my cousin and say:

“I think I broke the computer…”

While the screen looked completely out of control.

But here’s the thing…

I wasn’t just playing.

I was experiencing something I didn’t understand… but desperately wanted to.

And that planted a question in my head that never really went away:

“How does this actually work under the hood?”

When playing turns into discovery

Time passed.

And the computer stopped being just curiosity… it became fun.

Games came into the picture.

And with them… something that changed everything:

mods.

Now think about this…

You play a game… and then realize you can modify it.

Change files. Alter behavior. Break things… and try to fix them later.

That was a turning point.

Without even noticing, I stopped being just a user.

I started exploring the system.

Even if I didn’t have a name for it yet.

The “old-school nerd” influence

At the same time…

Movies. The Matrix. Hacker culture.

Systems, code, security…

It didn’t feel like just entertainment.

It felt like a glimpse into something bigger.

Like there was an entire world behind the screen… and I was only seeing the surface.

And that made the curiosity even stronger.

But there was a problem.

I had curiosity…

but no direction.

The first attempt (and the reality check)

Then came that classic moment:

“I need to learn programming.”

After the Minecraft boom, a friend told me:

“dude, try learning Java.”

It sounded simple.

I tried.

Opened it… read… tried to understand…

And… nothing.

Nothing made sense.

Variables? Classes? Methods?

It felt like staring at a completely different language.

And then what happens to a lot of people… happened to me:

I gave up.

Time passes… but some things stay

Years went by.

But that feeling from the beginning?

It never left.

The curiosity. The need to understand.

It only got stronger.

And that’s interesting…

Because some things you can ignore for a while.

But not forever.

Until one day, a simple clarity hits:

“This is what I want to do with my life.”

Not because it looked promising.

But because it made sense.

And this time was different.

I didn’t just try to learn.

I decided to learn.

What I do today

Today, I work with real-world software development.

Not just building things that “work”… but systems that need to keep working under pressure.

The kind of environment where:

a small bug can break an entire flow
a slow query can impact thousands of users
and a bad decision today becomes technical debt tomorrow

On a daily basis, I work with things like:

React, Next.js, Angular, and TypeScript on the frontend
Java with Spring Boot on the backend
Node.js in some scenarios
Python for scripts when it makes sense
Databases like PostgreSQL, MySQL, and MongoDB
Docker, Kubernetes, and cloud (AWS, etc.)

But more important than the tools…

is the thinking behind them.

Because in the real world, it’s not about knowing what to use.

It’s about understanding why something breaks… and how to fix it.

And let me be real with you…

Some of these I use every single day.

Others I’m still exploring more deeply.

And that matters.

Because in the real world, nobody knows everything — we evolve as new problems show up.

That’s the game: continuous growth.

Outside of that…

I’m genuinely passionate about technology as a whole.

And when I say technology… I don’t just mean code.

Games, hardware, the universe, artificial intelligence… all that “core nerd” stuff.

You know that kind of person who starts researching one thing and ends up reading about black holes at 3 AM?

Yeah… that’s pretty much it. 😄

Now think about this…

If even someone working with this every day still runs into doubts, traps, and hard decisions…

what about someone who’s just getting started?

Let me ask you something real quick…

Have you ever tried learning something in programming and felt like you were just “copying code” without actually understanding what was going on?

Or worse: everything online felt either too basic… or way too advanced?

If that’s ever happened to you, you’re not alone.

And that exact frustration is what pushed me to create this blog.

The real (and often ignored) problem

Let me challenge you a bit.

Most programming content teaches you what to do.

But almost never explains:

why it exists in the first place.

And that creates a silent problem.

You learn to use tools… But you don’t learn how to think.

The result?

You depend on tutorials
You struggle with new problems
You feel like you’re not actually improving

Does that sound familiar?

The turning point

Over time — studying, practicing, failing…

Something else started to happen.

I began explaining what I was learning.

To friends. To people around me. To anyone interested.

And then came an unexpected realization:

Teaching made me understand better.

Because when you explain something…

You see where you’re still confused. You organize your thoughts. You connect the dots.

I learn more. And so do you.

That’s exactly where this blog was born.

What this blog is about

This blog exists for one simple reason:

to teach you how to think like a developer.

We’re not just going to write code here.

We’re going to understand:

the problem
the reason behind the solution
what’s happening under the hood

Always following this flow:

A real problem
Where it breaks
Why the solution exists
Practical application

No skipping steps.

A quick example of what I mean

Imagine this:

You learn how to call an API using fetch.

const response = await fetch("/api/users");
const data = await response.json();

It works.

But now think about it…

What if the request fails? What if it takes too long? What if the user leaves the page halfway through?

Do you know what your code would do in those situations?

Or are you just assuming everything will go right?

That’s where the real world begins.

And that’s exactly the kind of thing we’re going to explore here.

Where this shows up in real life

You’ll see this everywhere in real systems:

APIs that need to be resilient
Interfaces dealing with state and errors
Architectures that need to scale
Code that other people will maintain

It’s not about pretty code.

It’s about code that actually works in the real world.

How things work “under the hood” in this blog

Nothing here is going to be thrown at you randomly.

Every piece of content follows a clear logic:

build context
create curiosity
explain clearly
show it in practice

Because learning isn’t about memorizing.

It’s about understanding.

When this will help you (and when it won’t)

This content is for you if:

you want to understand, not just copy
you want real growth
you like thinking about what you’re doing

Now, being honest…

If you’re just looking for ready-made answers with no effort, this might not be the right place.

And that’s okay.

Pros and cons

Learning this way gives you:

autonomy technical clarity consistent growth

But there’s a cost.

You’ll spend hours trying to understand something that could be copied in minutes.

You’ll think you understood… until a small variation breaks everything.

You’ll get stuck.

A lot.

And sometimes it’ll feel like you’re not progressing at all.

But that’s the part most people skip.

And ironically…

that’s exactly where real growth happens.

Simple summary

This blog is about:

understanding why things work thinking like a developer learning in a practical, real-world way

Conclusion

It all started back then.

In Paint. In CMD. In games. In curiosity without direction.

Today, it became a profession.

But more than that…

It became a continuous learning process.

And now let me ask you one last question:

Do you just want to learn how to code…

or do you actually want to understand what you’re doing?

If it’s the second one…

then you’re in the right place.