From a 14-year-old
coder to building
the market

I was 14 when I typed my first line of code. I don't remember what it did exactly — something in Visual Basic, something that barely ran — but I remember the feeling. The screen doing exactly what I told it to. Nothing in the world had ever felt that clean. I thought I'd found the thing.

I became obsessed. Algorithms, data structures, staying up until 3am learning things nobody asked me to learn. I genuinely believed that if you wrote better code than everyone else, you won. Full stop. The world would recognize it. Doors would open. That was the deal.

At 16, I got my first job as a developer. Real code, real deadlines, real teammates. I was the youngest in the room by a decade and I worked like I had something to prove — because I did. I shipped fast, broke things fast, fixed things faster. Every senior engineer I watched, I reverse-engineered. Not the code — the judgment. The way they decided what mattered and what didn't.

The years between junior and senior passed in a blur of shipped features, late nights, technical interviews, and the slow accumulation of something you can only call taste. You stop asking "how do I build this?" and start asking "should we build this at all?" You get put in rooms with clients. You start understanding that the software is never the product — the outcome for the human using it is the product.

The world was bigger than Mexico and I knew it. So I did something most people from my background didn't do: I taught myself English. Not in a school. Not in a course. In the trenches — absorbing every podcast, movie, and Stack Overflow thread I could find, running calls with US clients while mentally translating in real time, pretending the gap wasn't there until one day it wasn't. It took years. It was worth every uncomfortable moment.

Once the language barrier fell, doors opened fast. Remote contracts with US companies. Salaries that felt unreal for someone who grew up watching that number from the other side of a screen. A career that proved the theory: being technically exceptional and able to communicate it in the language of your clients is a combination most people never build. I had built it. Life was good. Very good.

And then came the hardest decision I've made professionally: walking away from it. Not because I was unhappy. Because I understood, at some point, that I was optimizing for comfort instead of potential. A salary tells you exactly what you're worth to someone else. I wanted to find out what I was worth to myself.

Then I built my first thing for myself. A side project. Something I believed people needed. I poured everything I had into it — clean architecture, tests, CI/CD, the works. Nobody came.

That silence was the most important teacher I ever had. Not a professor, not a tech blog, not a senior engineer. The silence of a product with zero users is a very specific kind of feedback. It says: you built for yourself, not for them. You shipped, but you didn't sell. You created supply and forgot to create demand.

So I started learning marketing the same way I learned programming — obsessively, from first principles, by doing. Cold emails. Proposal pages. Landing pages at midnight. Outreach automations. Referral systems. I studied conversion like I used to study algorithms. I tracked funnels the way I used to track memory leaks. Slowly, things started to move.

The agency — Rocha Studios — came from that collision. Engineering discipline applied to marketing. Systems thinking applied to growth. The obsession of a developer combined with the survival instinct of someone who'd seen good products die in silence. Every product below is a chapter in that story.