I have been working on mastra-azure-ai-search, an Azure AI Search vector store provider for Mastra.

The reason is simple: I opened the integration work upstream in Mastra, but the PR has not been approved yet. Rather than keep the adapter blocked inside a pending pull request, I decided to publish it as a standalone package so it can be used, tested and improved now.

Cardboard Architecture: when code looks clean but nobody understands it​

Some projects give a great first impression when you open them:

• Well-organized folders: core, domain, infrastructure, services, helpers…
• Classes with serious names: UserService, OrderManager, PaymentHandler…
• Extensive documentation, diagrams, detailed README…

And yet, when you try to follow how the system actually works, you find something very different: methods calling other methods calling other methods, layers that only delegate, business logic scattered across the repository… and you thinking:

“This looks architectural, but understanding it is painful.”

That’s what I like to call cardboard architecture: it looks solid on the outside but doesn’t really hold the weight of the business inside.

Two ways to build production AI agents​

In recent months many frameworks for building AI agents have emerged. Two approaches I find particularly interesting are:

• Mastra, an all-TypeScript agent framework that feels natural if your stack is Node-based.
• Microsoft Agent Framework + Azure AI Foundry (Azure AI Agents), Microsoft's offering that pairs an orchestration library with a managed agent service on Azure.

At first glance they look like different worlds, but they share a similar mental model: agents that keep conversations via threads/sessions, messages, and runs.

In recent years, I've seen two equally damaging extremes in many development teams: over-engineering and the eternal PoC culture. This post is about why both extremes are bad engineering practices and how to find a reasonable middle ground.

Hello and welcome to my personal blog! 👋

This is the first post of many to come. Here I'll share my experiences, learnings, and reflections about technology, software development, and everything I'm passionate about.