Skip to content

Chapter 03

Starting Again

What happened when the original dream ended?

4 min read


There is something strangely uncomfortable about beginning again.

Not because starting is difficult.

Because starting again usually means admitting that the first plan didn't work.

When I decided to move away from my childhood dream, I wasn't suddenly filled with confidence.

I wasn't inspired.

I wasn't certain.

I was simply searching for another direction.

Sometimes that's enough.


When I joined college, I chose Networking.

At the time, programming felt impossible.

Whenever I looked at code, it felt like another language that everyone else somehow understood except me.

Networking felt more practical.

More predictable.

It made sense.

Programming didn't.

If someone had told me then that one day I would build websites, lead technical projects, and spend my days solving product problems, I probably would have laughed.

Life has a funny way of introducing us to the things we're trying to avoid.


Eventually, I joined Code Pros.

Looking back now, I don't think I realized how important that decision would become.

At that moment, it was simply an opportunity.

Another chance to begin.

I wasn't experienced.

I wasn't confident.

I was just willing to learn.

That willingness turned out to matter far more than experience.


Memory

The Copied HTML File

One of my earliest tasks was to build an HTML landing page.

There was only one small problem.

I didn't actually know how to create one.

So I did what many beginners secretly do.

I opened a teammate's HTML file.

Copied everything.

Code Pros

Deleted the parts I didn't understand.

Then slowly started replacing pieces until something began to resemble my own work.

At the time, I wasn't proud of that process.

I thought it meant I wasn't good enough.

Today, I smile when I remember it.

Because every developer has a version of that story.

Mine just happened to begin with a copied HTML file.


Something unexpected happened after that.

As I kept repeating the same setup, I slowly started understanding why each piece existed.

The structure became familiar.

The repetition became confidence.

Eventually, I stopped copying.

I started building.

Then one day I created my own HTML boilerplate.

It wasn't meant to become anything important.

It simply saved me a little time.

Soon, other teammates started using it too.

The thing I built while I was still learning ended up helping people around me.

That experience quietly changed the way I thought about learning.

You don't need to be an expert before creating something useful.

Sometimes beginners build tools that beginners need.


Of course, not everything became easier.

JavaScript made almost no sense to me.

Even CSS had a way of making simple things feel complicated.

I still remember staring at display properties, wondering why elements refused to behave the way I expected.

Some days, I questioned whether I had chosen the wrong path all over again.

The feeling was familiar.

It sounded a lot like the voice that had followed me after my Army dream ended.

"What if you're simply not meant for this?"


Fortunately, that voice wasn't the only one I listened to.

Whenever I got stuck, I searched.

Documentation.

Stack Overflow.

YouTube.

Udemy.

Forums.

Anything that could teach me one small piece I didn't understand yesterday.

Learning wasn't one big breakthrough.

It was hundreds of tiny breakthroughs that slowly connected together.

One solved problem became another.

One concept unlocked the next.

Progress rarely felt dramatic.

But it was happening.


Something else happened during those months.

The more I learned about HTML and CSS, the less I cared about memorizing code.

I became fascinated by structure.

Consistency.

Design principles.

Clean implementation.

I realized good development wasn't just about making something work.

It was about making something understandable.

That mindset would stay with me long after the code itself changed.


Eventually I found myself leading one of our Bootstrap 3 projects.

If someone had shown that future to the person who copied a teammate's HTML file on his first task, he would never have believed it.

The gap between those two versions of me wasn't talent.

It was repetition.

Patience.

And the decision to keep showing up, even when learning felt slow.


Looking back today, I don't think choosing Networking instead of Programming was a mistake.

It taught me something far more valuable.

A degree doesn't decide what you become.

Curiosity does.

Opportunities do.

Consistency does.

The classroom gave me knowledge.

Life gave me direction.

And somewhere between the two, I quietly became someone who wasn't afraid to begin again.

Every new beginning asks the same question.

"Are you willing to be a beginner one more time?"

For me, the answer slowly became yes.

That single word changed everything.

Because not long after that...

I found a place that believed in me before I fully believed in myself.

You have reached the end of Chapter Three.

Take a breath.

Continue when you’re ready.

Open Chapter Four →