Childhood
I grew up in a small town in Entre Ríos, Argentina — a flat landscape of farms and endless plains. Most of my early memories are tied to that life: animals, early and cold mornings and farm work. That was the world around me.
So, how did I end up spending most of my life in front of a screen?
Beyond my love for animals and open field, I was always drawn to the computer. Games were my gateway, but I was restricted on not having a good PC at home.
One day, at my grandma’s house, I found an old CD with a bunch of random software — the kind from magazine collections. On it were Warcraft 3 and Doom. I was maybe nine. Installing them changed everything, Warcraft 3 quickly became my all-time favorite game, and also my fanaticisim for fantasy.
Youth
By the time Counter-Strike 1.6 and MU Online were peaking here, everyone was hooked. The cyber cafes were packed — dim rooms packed with the glow of CRT monitor, sticky keyboards and it’s own characters (if you are from Argentina, you know what I am saying).
My days had a routine: meet with friends, skate/bike/football, hanging out at cibers and finish the day watching movies that we rented on the video clubs.
As I mentioned, I had a terrible PC at home, and my dad didn’t love the idea of me sitting for hours playing games. But I didn’t care. I played at 15 fps and loved every second of it.
Soon, I found myself deep in the community side of gaming — moderating Counter-Strike forums, managing a few servers with friends, organizing events, even selling admin roles. Looking back, that was my first real step into the technical side of computers. I was editing configuration files, tweaking server parameters, and experimenting with Cinema 4D and Photoshop (back then the big thing was called “GFX design”).
This is one of the design that I saved from my Facebook page.
I was still a kid, but that world pulled me in. My bad computer also pushed me down the optimization rabbit hole — I spent hours on forums learning how to squeeze a few extra frames out of the same hardware.
Those early days of the internet were something else — messy, anonymous, but deeply human. Everyone had something to share, and it all felt authentic.
I was everywhere online, around games, around communities. I’ll admit it — I cheated in some of them (sorry). But even that got me closer to understanding how things worked beneath the surface. By age twelve, I wasn’t just playing anymore. I was exploring.
By the end of high school, I had to choose what I was going to study. Without thinking too much, I watched a few programming videos, installed Eclipse, and printed my first “Hello World” in Java. I was so happy to see that the machine was actually doing what I told it to do. That moment was enough — I decided to go for Software Engineering.
Later
I started college, studying Software Engineering, and soon the first programming classes began. I was amazed. I still remember the first time I understood recursion (or at least I think I did…) — it was while coding the Fibonacci sequence, that classic exercise. I instantly fell in love with math and logic.
Back home, I spent hours doing exercises, and eventually, I discovered p5.js and The Coding Train channel on YouTube — all about creative programming. It opened up a whole new world for me. I went from seeing plain numbers in the terminal to actually watching things move on the screen, all following math and logic from my classes. I was fascinated.
I spent countless nights building small projects, simulating physics, experimenting, learning by doing. Most of what I know about object-oriented programming came from working with p5.js — such an amazing library — and from The Coding Train, which is still one of my favorite channels.
That curiosity naturally led me into game development. I already had some experience with Cinema 4D, so I was a bit familiar with graphics, or at least the technical side of it. Then I started experimenting with Unity — nothing fancy, but it felt like stepping into yet another world, what I enjoyed was creating everything from scratch. My first big project was in Processing, a Solar System in 3D, trying to recreate it at scale.
Professional Path
I wanted to work, so I started looking for internships. My first job was at the university, doing Help Desk support. After that, I got my first professional position at a multinational company — AMC Networks, the producers of Breaking Bad and The Walking Dead. I joined the marketing team, mostly working on front-end development for campaign websites, which had a strong creative side to it.
That’s where I found a way to connect programming with creativity again. During a Walking Dead campaign that had an 8-bit retro style, I asked if I could contribute by making a small game in the same visual tone — and they loved the idea. That became my first use of p5.js in a professional project. I was really proud of it: a mini-game where all the sprites and animations were made from scratch.
Lil screenshot from the game
Summarizing
To finish this story — my path continued in the web development world. I started working on the backend, combining everything I’d learned and finding ways to bring creativity into every project I joined. At one point, I even redesigned Kelsus using Three.js with 3D models, and Framer Motion — combining animation, design, and interaction.
Three.js felt like the super-powered version of p5.js — well, not really, but that’s how I saw it when I first started learning. I loved experimenting, building prototypes, side projects, and mixing everything I knew into something new.
Over time, I joined bigger projects, working on infrastructure, optimization, and performance — mostly on the frontend, but I also got to dive into the backend. My professional work pulled me more toward the technical side, but my favorite part has always been creating — thinking, improving, and making things move fast. That’s still what drives me every day.
You can check my LinkedIn for more details about my professional path — this blog was more about how I first stepped into programming, so I’ll leave it here.
Thanks for reading.