Why I'm starting this blog

I've spent 12+ years building and scaling software in banking, fintech, insurance and e-commerce. Almost everything I know I learned by making decisions with incomplete information, in front of a team, a client or a dashboard gone red. This blog is where I'm going to write it down.

#What you'll find here

• CTO Log. What really happens in the CTO seat: architecture decisions, hiring, incidents, roadmaps that change mid-quarter, and what I'd do differently.
• Launches. The products I build or lead, why they exist and what problem they solve.
• Signals. Industry news, read with one question in mind: what does this mean for a startup or an SME that has to decide with a small team and little time?

#Who I'm writing for

Founders who have to make technical decisions without being technical, product teams growing faster than their architecture, and other CTOs who want to compare notes.

#How I'll write it

Short, concrete, no fluff. If there's a number, it's one I can stand behind. If something went wrong, I'll say so. And I won't publish anything confidential about the clients I work with: when I talk about a case, it will be with their permission or abstracted enough that it can't be recognised.

I write in English and Spanish. If something here is useful to you, or you disagree, message me on LinkedIn or book a call: the best ideas for a post always come out of a conversation.