The Most Important Code I Have Ever Written Was Never on a Computer

Some questions seem simple until you actually try to answer them.

Not long ago, someone asked me why I love technology so much.

My first instinct was to talk about artificial intelligence, software architecture, programming, distributed systems, and all the conversations that naturally happen when you spend your life building software. After all, I've spent a large part of my life surrounded by computers—writing code, reading documentation, learning new tools, and trying to understand how things work.

But the more I thought about it, the more I realized that none of those things truly answered the question.

And, strangely enough, the answer started to reveal itself during the 2026 FIFA World Cup.

As I watched Cristiano Ronaldo play, I couldn't stop thinking that I was witnessing one of the final chapters of one of the greatest careers in sports history.

For the first time, I wasn't watching the match.

I was watching the journey.

Instead of focusing on the goals, the trophies, or the records, my mind drifted toward everything that happened long before those moments existed.

The years of training.

The sacrifices.

The injuries.

The difficult decisions.

The discipline required to stay among the world's best for more than two decades.

Then one question stayed with me long after the final whistle.

What does a person truly leave behind when a career like this comes to an end?

I've always admired Cristiano Ronaldo, both on and off the field.

On the field, his achievements speak for themselves. Very few athletes have managed to remain at the highest level across multiple generations, constantly reinvent themselves, and continue competing long after many of their peers had retired.

But, honestly, that's not what inspires me the most.

What truly inspires me happens when the stadium is empty.

I admire the discipline with which he chose to live.

The willingness to train as if he were still fighting for his first opportunity.

The obsession with improving just one percent every day.

The commitment to taking care of every detail, even after proving everything he needed to prove.

While millions of people remember his goals, I find myself thinking about the thousands of hours no one ever saw.

The early mornings.

The endless repetitions.

The quiet sacrifices.

The days when he probably didn't feel like training either—but showed up anyway.

Because extraordinary careers are never built during ninety minutes.

They're built during the countless ordinary days when it feels like nothing is happening.

We live in a culture obsessed with results.

We celebrate product launches.

Championships.

Funding rounds.

Successful startups.

Promotions.

Awards.

Viral moments.

But we rarely talk about the silent process that made those moments possible.

And yet, that's where everything important happens.

As I reflected on that idea, I couldn't help thinking about my own profession.

Because software development works exactly the same way.

Nobody congratulates a team for writing great automated tests.

Nobody celebrates a well-designed architecture.

Nobody posts about the weeks engineers spent understanding a problem before writing the very first line of code.

Users only experience the outcome.

And that's exactly how it should be.

The best software is the software whose complexity remains invisible.

When an application works beautifully, no one thinks about the architecture behind it, the design decisions, the countless debugging sessions, the code reviews, or the trade-offs that made that experience possible.

The most valuable work is often the work nobody notices.

Maybe that's why, as the years go by, I find myself admiring quiet work more than ever.

The work that doesn't go viral.

The work that receives no applause.

The work that doesn't need recognition.

Because that's where lasting things are built.

And that's when I finally understood something.

Technology was never the destination.

It was only the path.

What truly captivated me wasn't programming languages, frameworks, or the excitement of building applications.

What changed my life was the way this profession gradually reshaped how I think.

When you first learn software development, you believe it's all about writing code.

That's perfectly normal.

You spend months learning syntax, design patterns, databases, and trying to make your application run without crashing every five minutes.

Eventually, you realize that was only the surface.

Programming has never been just about telling computers what to do.

Programming teaches you how to think.

It teaches you how to face problems that initially seem impossible and break them into smaller pieces until each one becomes manageable.

What's fascinating is that this mindset eventually escapes the screen.

Without realizing it, you begin approaching life the same way.

Problems stop looking like mountains.

They become a collection of smaller challenges waiting to be solved.

That was probably the first great lesson technology gave me.

The second came when I realized how incredibly fast this industry evolves.

For years I chased technologies as if each new framework or programming language held the ultimate answer.

I'd finally learn one.

Then another would appear.

I'd become comfortable with a framework.

Months later, a new one would promise to change everything.

The same happened with methodologies, cloud platforms, architectures, and now artificial intelligence.

At first, it was frustrating.

It felt like I was never enough.

There was always something else to learn.

Always another step to catch up.

Until one day I stopped competing against the speed of technology and started observing something else.

Some engineers adapted effortlessly.

It didn't matter whether a new language, a new platform, or an entirely new paradigm emerged.

While everyone else panicked...

They simply learned.

That's when I realized something that completely changed my perspective.

The real value was never in memorizing tools.

The real value was becoming the kind of person capable of learning any tool.

That difference may sound subtle.

But it changes everything.

Because tools change.

The ability to learn endures.

Somewhere along that journey, another source of inspiration found me.

Japanese philosophy.

Not because I believe it holds all the answers.

Nor because I want to romanticize a culture that is not my own.

What fascinates me is one particular idea.

The idea of living according to a personal code.

When I first learned about Bushidō, I realized that beyond the samurai, beyond history itself, there was a principle that could apply to any profession.

Choosing your values before circumstances choose them for you.

That realization connected everything.

Cristiano Ronaldo.

Technology.

Software engineering.

The samurai.

The ninja.

At first glance, they seem completely unrelated.

But the more I reflected on them, the more they all pointed toward the same truth.

Excellence never appears overnight.

It is built quietly.

It is built when nobody is watching.

It is built through repetition.

Through patience.

Through discipline.

Through consistency.

Through countless small decisions that seem insignificant on their own but become extraordinary over time.

That made me think about something else.

Software developers write code every day.

But there is another kind of code we rarely talk about.

The code that determines how we react when a project fails.

How we treat teammates during code reviews.

How we respond when we discover we were wrong.

How we face problems that seem impossible to solve.

That code doesn't run on computers.

It runs inside us.

And over time, I became convinced that it is the most important code of all.

Today, artificial intelligence is transforming our industry faster than most of us imagined possible.

Some people feel uncertainty.

Others feel excitement.

I feel curiosity.

Because if technology has taught me anything, it's this:

Change has never been the enemy.

Our willingness to evolve has always been the real challenge.

AI will generate code.

It will automate workflows.

It will design systems.

It will solve problems we once considered impossible.

But there are things no technology can do for us.

It cannot build character.

It cannot choose discipline.

It cannot remain humble.

It cannot decide to keep learning when nobody expects it to.

It cannot develop a philosophy for living.

Those things remain profoundly human.

And perhaps that's the most valuable skill of the future.

Not mastering the next framework.

But becoming the kind of person capable of mastering any framework.

Not depending on today's technology.

But building a mindset capable of adapting to tomorrow's.

Over the years, I stopped seeing software development as just a profession.

I began seeing it as a lifelong practice.

Every bug tests my patience.

Every project challenges my organization.

Every code review teaches humility.

Every conversation with other engineers expands my perspective.

Every mistake reminds me how much there is still to learn.

Maybe that's why I continue to love this journey.

Because while most people think my job is writing software...

I feel like I'm doing something much deeper.

I'm learning how to think.

I'm learning how to solve problems.

I'm learning how to live with uncertainty.

I'm learning how to adapt.

I'm learning how to build.

But most importantly...

I'm slowly writing the person I want to become.

And I think that's the answer I had been searching for all along.

Technology didn't simply change my career.

It changed the way I see the world.

It taught me that knowledge matters.

But character matters more.

That tools evolve.

But principles endure.

That the most meaningful work happens far away from the spotlight.

And that the greatest things are always built long before anyone notices them.

Maybe that's why this World Cup meant so much more to me than I expected.

I didn't just watch one of the greatest football players in history.

I witnessed the result of a life built on discipline, consistency, and principles.

And I realized that every one of us is writing two kinds of code.

One lives inside our repositories.

The other lives inside our daily decisions.

The first one will eventually be replaced.

Refactored.

Deleted.

The second one becomes who we are.

And I have a feeling that will always be the most important project of my life.