Hello and welcome! My name is Guillermo Uranga, though many know me as Memo Uranga. I'm Mexican, thirty-six years old, and yes, I couldn't be more millennial if I tried.

Today I want to welcome you to "Beyond the Code," a space born from a personal and professional concern I've had for a long time in my experience as a software engineer.

On the internet, we find countless blogs, tutorials, and courses about how to write code, learn programming languages, develop specific modules, and even how to build companies and develop projects. There's an overwhelming amount of technical resources for learning how to program or become an "entrepreneur."

But what about everything that surrounds the code? What about that pressure, those challenges, those decisions and experiences that go beyond the lines of programming? I've always loved Legos. I enjoyed building them. But there came a moment when I asked myself: "what else?" Building a Lego is fun, but once finished, all that remains is the development, the experience of having assembled it.

Something similar happens with code. It's fascinating to create a test program that works perfectly, but when you decide to take it further, when you want to turn it into a real product, everything changes.

It's no longer just about making the code work. Now you must consider:

And then, when users start using it, you get:

Then you need more help, perhaps create a company, face regulations, reinvent your ideas... You discover that something works, but it could have been done differently to be more scalable or efficient.

And that's what this blog is about. Yes, it's great to build things, write code, develop projects. But why do we create them? What does it really entail to make them? What does it mean to start a business, a company, or even a simple digital "toy"? How do you capitalize on it? What happens when this becomes your life, your daily routine?

Interestingly, every project is born from a personal need, or at least in my opinion, these are the best ones. And just today, when I had the idea for the name and bought the domain, I decided to develop my own blog or CMS (Content Management System) instead of hiring a customized service. After all, I'm an engineer, I like to build, and this blog will be about that—why not make it practical?

When deploying the first update, a very simple one—just the logo validating that the essentials work on the web—I encountered a small error that wouldn't let me continue. After two hours of frustration, it turned out to be something extremely simple: lack of space on my own machine, a machine that shouldn't be out of space, but it turned out I had limited my Docker and hadn't purged it. Such a simple error that even AIs couldn't give me a precise explanation. I simply needed to increase the space or purge Docker for the container creation to work correctly.

So a project as "simple" as creating a blog—actually, just setting up the initial services, something I've done many times—consumed two hours when it could have taken ten minutes. And yes, like everyone else, one has personal, family, work, and mental life, and sometimes not focusing on a specific task leads to simple errors. In the end, it's not rocket science; it's just about focusing.

The point is that errors can consume hours or days when they could really be resolved in minutes due to lack of concentration, and with that, I just realized that I precisely needed to create this blog.

The page is currently very simple, and I intend to keep it that way, although I'll update it over time to practice and exemplify topics we discuss in the blog. Some posts will be about specific code; others will talk about experiences and challenges, both technical, project-related, or life experiences. I want it to be a dynamic blog, with texts, sometimes videos, code, and always with a focus on what lies beyond the code.

Welcome to this journey. I hope you find value in my experiences and learnings,

Memo Uranga