Let me brag a little

Laravel is the best framework ever, in any language, everywhere. Not everyone is going to agree with that, specially not the people who think that "PHP is Dead". But what can I say, I have tried countless frameworks, and there isn't any that has captured my heart quite like Laravel.

The developer experience, the design patterns, the architecture, and the cohesive ecosystem are the best I've seen. In fact, I'm always trying to incorporate ideas from Laravel in other languages and projects. If I could build everything with Laravel, I would!

I've tried my fair share of frontend frameworks (I started working in the jQuery era!). But Vue has always been the one that felt more like home. I think it has the perfect balance of ergonomics, simplicity, and power.

As much as I like Laravel, my favorite part of the stack is the frontend. I always get the most excited when I work on product and user experience, so Vue has been my perfect partner in crime.

Solid is definitely the lesser known of the list. You'll notice there isn't a database in my stack, but I really mean it when I said that I could build anything! Solid is how I think data should work in most applications.

I have written plenty about it in this site, but in case you don't know what it is, the short version is that it's a decentralized storage protocol built by the inventor of the Web. Or, as I see it, the natural evolution of the Web according to its original vision.

In contrast with the rest of technologies here, I wasn't immediately enamored of TypeScript when I first tried it. But it's been growing on me, and as I got more proficient, I started missing it when it was gone.

Luckily, JavaScript can really run anywhere, and I could just write TypeScript for the rest of my life. Alas, it's not Laravel, and sometimes I would agree it's too verbose and convoluted.

I live and breathe the Web. I've always worked in user-facing products, and all the work in the background has always been in service of that. Maybe that's why I'm a lot more interested about the Frontend than the Backend. But I'm definitely the most comfortable when I can contribute across the stack.

I've also worked in other platforms, particularly in mobile, but most of the time it's also been using web technologies (with the occasional native development for plugins and debugging).

I haven't formally worked as a Design Engineer, but looking at the job landscape it's one of the roles that I like the most. I have always been very keen on the user experience, and even though I'm not a designer, I really like design and interacting with designers.

If you want to judge my design skills, you can look at this website and my side-projects. For these, I'm 100% responsible for the design (and everything else!).

Ever since I started programming, I've been interested in Software Architecture. My involvement in startups and personal projects has also given me plenty of experience looking at systems in aggregate, and I've often lead shifts in architecture and built systems from scratch.

I like to think outside the box, and I often challenge assumptions. I'm always thinking about the best way to solve a problem.

Given my entrepreneurship and passion about software, I've always had a product mindset when it comes to engineering. I'm always trying to understand the end goal of my work, and I like to go beyond simply solving technical problems.

Sometimes, the best solution to a problem is to avoid it entirely. You may not need that feature!

If you look at my work history, something you may find interesting (or uncommon) is that I rarely use the same stack. I always learn new concepts quickly, and ever since I learned it in university, programming has felt like second nature.

Because of that, I'm always up for learning new technologies, and I consider myself a life-long learner.

If you don't know Moodle, you should know that it's the most used LMS for schools and higher education; and one of the most used Open Source projects in the world.

At Moodle, I had the opportunity to work on software used by millions of people. In particular, I worked in the Mobile Apps team, which had the unique challenge of having to support a very complex platform in low-end devices. And all of that with full offline capabilities.

Other than the tech, Moodle is a company whose values and ethos are strongly aligned with mine, and it was a joy to spend 5 years working there. Still, all good things come to an end. If you're curious about my decision to leave, I wrote about it in my blog: The End of The Chapter.

I've been involved in a couple of startups in very early stages, but I would say Geemba is the one I'm most proud of.

This was one of the few projects where I had full control of the technical stack and decisions, and I built it all from scratch: a pay-per-minute billing and access service, multiple cross-platform applications, a rules-based workflow assistant, etc. I learned a lot in the process, and to this day I still consider it some of my best work (it's a shame that nobody is going to see it!).

So yes, it's a failed startup, but I'm still very proud of what we did :). If you're keen to learn more, you can check out its project page.

I guess technically my side-projects are not part of my career (that's why they are called side-projects 😅). But I still think they contain some of my best work. And hey, you can see at all of it, because it's all Open Source! You can also be sure that I'm 100% responsible for everything: design, code, taste.

You can find all about them in my projects page and throughout this site, but if you just want some of the highlights check these out:

• Umai
• Focus
• Soukai
• AerogelJS (Still a WIP, but I'm really fond of it!)
• /now (If you scroll down, you'll find an activity log of my 10+ years online)