A sustainable pace
One main issue every two weeks, with short notes whenever a lesson is worth sharing quickly.
Newsletter
A personal newsletter about technical leadership, architecture decisions, product, applied AI and real lessons from building in Latin America. Issues are sent in Spanish; the archive is translated here.
Every issue has a practical idea, a real experience and a concrete question to think more clearly about how we build technology, products, teams and businesses.
Subscription
Leave your email, pick your main interest and I'll add you to the list for upcoming issues. Issues are written in Spanish.
Cadence
One main issue every two weeks, with short notes whenever a lesson is worth sharing quickly.
Who it is for
Operational status
The public page, the archive and the editorial sequence are already defined. Real subscriptions are connected to a secure Worker with consent, and the first welcome flow is ready to activate when sending starts.
Editorial pillars
Technical and human leadership
Autonomy, growing Tech Leads, difficult conversations, engineering metrics and sustainable teams.
Engineering and platforms
Architecture, APIs, platform engineering, observability, security and decisions with real operational impact.
Applied AI
Spec-driven development, agents, MCP, automation and the practical limits of AI in software teams.
Products and ventures
Discovery, MVPs, hypotheses, pricing, learning in public and how to decide what is worth building.
Fintech, payments and business
Subscriptions, webhooks, financial APIs, security, compliance and the trade-offs of the regional ecosystem.
Technology and life
Music, pets, creativity and personal experiences that turn into useful lessons for building better.
Public archive
Each issue connects a real experience, a practical idea and a bridge to the rest of the ecosystem: blog, projects and conversations.
Issue 002
When an idea is still blurry, racing straight into code tends to look like progress. Often it's just an expensive way of postponing the conversation that was missing.
Issue 001
A webhook isn't a friendly notification: it's an operational edge where a payment system either stays consistent or starts losing trust.
Welcome sequence
Email 1
A short introduction, what kind of ideas they will receive, the expected cadence and a question to tag their initial interest: leadership, architecture, AI, product or payments.
Goal: Explain the editorial promise and ask for a simple reply about the subscriber's main interest.
CTA: Reply with the topic that matters most to them today.
Email 2
How banking, fintech, leadership, my own products and applied AI come together in a single professional practice: translating real problems into sustainable decisions.
Goal: Connect background, judgment and curiosity without sounding like a corporate bio.
CTA: Reply with the hardest problem their team still can't explain well.
Email 3
A selection of articles and cases by topic: leadership, platform, applied AI, product or payments. Each link explains why it is worth opening.
Goal: Offer three ways in based on the reader's stated interest.
CTA: Choose a topic to explore in upcoming issues.
Email 4
A short presentation of Milo Care, MiCuota.online, WebspecAI and Pambú Tech, with a question about which of the reader's hypotheses or products deserves a conversation.
Goal: Show real projects as a source of learning, not as advertising.
CTA: Share feedback or ask for context about one of the projects.
Email 5
An explicit invitation to reply if their interest is leadership, architecture, product, collaboration, press, events, investment or a professional opportunity.
Goal: Open a direct relationship and classify the kind of conversation that could come out of it.
CTA: Reply with the kind of conversation they want to start.