The begining:

My story begins back in 2015; I was young and had been passionate about video games since I was very little. I was about to start high school when a question struck me: How are games actually made?

I soon realized that making a game is quite an odyssey—creating sprites, composing music, designing interfaces, writing code... and the code—that was what captured my attention the most. I had loved computers since I was very young; by the age of 12, I was already capable of formatting my PC to switch operating systems—and had already managed to infect it with my first Trojan virus.

So, I continued delving into the world of programming. It was tough at first; programming had nothing to do with simply installing Windows XP or Windows Vista—it was something that went far beyond that.

The first tools I discovered were Unity3D and GameMaker. Unity felt far too complicated for me at the time, so I decided to use GameMaker instead. I remember how, after countless attempts, I finally managed to create a replica of the *Pokémon* intro featuring Professor Oak.

The High school:

As time went by, high school proved invaluable in helping me gain a deeper understanding of programming and software in general. This knowledge greatly facilitated everything that followed—specifically, my transition to Unity.

Throughout high school, I spent a great deal of time working with Unity. I was still a complete novice, so my abilities were largely limited to shuffling cubes around, and I struggled incessantly just to get my character to move using a third-person control scheme. I dreamed of creating my very own *Zelda* game—though, of course, that ambition never progressed beyond a simple, bug-riddled prototype.

University:

More time passed, and I enrolled in university to pursue a degree in Computer Systems Engineering. It was there that my knowledge of computing—in the broadest sense—skyrocketed. It was no longer just about writing lines of code, but about building complete systems: servers, networks, databases, and both front-end and back-end development.

Two specific courses—Software Engineering I and II—were instrumental in helping me grasp the full software development lifecycle. I came to understand that simply sitting down and writing code isn't the whole story; you have to start with an idea and craft a comprehensive plan from start to finish, encompassing every stage: planning, development, testing, and launch.

Nearly five years have passed since I graduated as a Computer Systems Engineer. Since then, I have learned to build complex systems—such as game inventory, quests, and simple combat systems—and have also come to appreciate the importance of creating tools to streamline my workflow; you can see this reflected in some of the projects in my portfolio.

I continue to hone my skills and learn as I search for my first position as a video game developer.

The following is a list of languages, engines, frameworks and software I've worked with and have a minimum knowledge of.

These lists follow this legend:

Unfortunately, I have not yet been able to land my first job as a video game developer.

My current Job
I've been working as a dispatcher at a warehouse in Texas, USA as part of Expeditors for almost 5 years now.

Im in charge of doing physical inspections to ensure that outgoing shipments are properly loaded and documented to be exported to Mexico.
During all this years I've proven to be able to work under moderate preasure and a priority based workflow along with my co-workers and proven I'm easy to work with.