Before creating digital products, I was a designer.
And before that, I played bass.
It all started with music. Playing bass led me to design posters, T-shirts and album artwork for the bands I played with. Soon after came my first websites. Without realizing it, I had found a way to bring creativity and technology together.
I think of development as a form of craftsmanship.
Over time, I realized that writing code was only part of the job. What really mattered was understanding problems, designing solid architecture, and creating solutions that could evolve over time.
I like spending time thinking through the structure before building anything. Choosing the right solution, taking care of the design, writing readable code, optimising performance and removing everything that doesn't add value. Small decisions that, accumulated over years, end up making the difference.
That way of working eventually became my own ecosystem of tools. They weren't created to be sold, but to solve real problems that kept appearing again and again across projects.
Today I build digital projects guided by the same idea that inspired me to start: understand the problem before writing the solution.
What I consider essential in any digital project.
See how I build a project →-
Arquitectura antes que código.
Una buena solución empieza mucho antes de escribir la primera línea.
-
Rendimiento desde el primer día.
La velocidad no es una optimización final. Forma parte del diseño.
-
SEO como parte del producto.
No se añade después. Se construye desde la arquitectura.
-
La IA no sustituye el criterio.
La utilizo para acelerar procesos. Nunca para dejar de pensar.
-
Todo debe poder evolucionar.
El mejor proyecto no es el que funciona hoy. Es el que sigue funcionando dentro de cinco años.
